Clean Architecture using Go Elton Minetto @eminetto

What is Clean Architecture? • https://8thlight.com/blog/uncle-bob/ 2012/08/13/the-clean-architecture.html • https://www.amazon.com/Clean-Architecture- Craftsmans-Software-Structure/dp/ 0134494164

Constraints • Independent of Frameworks • Testable • Independent of UI • Independent of Database • Independent of any external agent

Divide our code in 4 layers

• Entities: encapsulate enterprise wide business rules. An entity in Go is a set of data structures and functions. • Use Cases: the software in this layer contains application specific business rules. It encapsulates and implements all of the use cases of the system.

• Controller: a set of adapters that convert data from the format most convenient for the use cases and entities, to the format most convenient for some external agency such as the Database or the Web • Framework & Driver: this layer is generally composed of frameworks and tools such as the Database, the Web Framework, etc

Clean architecture using Go

No content

The package entity contains our entities

No content

In the package user we can find the other layers of our architecture

No content

In the file interface.go we have the interfaces of Use Case and a repository, that will store our entities.

No content

In the files repository_inmem.go and repository_mongodb.go we have two implementations of repository interface. The repository represents the layer Framework & Driver

No content

In service.go we have the implementation of Use Case

No content

The package api implements the Controller layer

No content

In the following snippet, from api/main.go, we can see how to use the service

No content

Now we can add other controllers, like a CLI app, lambda functions, bots, and so on.

And we can test our packages, layer by layer

pkg/user/service_test.go

No content

api/handler/user_test.go

No content

Example https://github.com/eminetto/clean- architecture-go

https://eltonminetto.dev @eminetto