clean-architecture-in-golang/

[utterances-bot]

Clean Architecture in Go | pkritiotis Software Engineering

This article covers the fundamentals of the Clean Architecture design concept and demonstrates how to apply its principles in Go through a simple web app implementation.

https://pkritiotis.io/clean-architecture-in-golang/

[Abdulmoiz-Ahmer]

Hey man awesome stuff. I have been trying to wrap my head around this architecture for a while now. This is by far the best article i have found on web. Also where do you think the validation and error handling would fit in this architecture?

[pkritiotis]

Hey @Abdulmoiz-Ahmer 👋 ! Thank you for the comment. I'm very glad you liked the article 😄 !

Validation and error handling is handled in each layer separately on the scope of their responsibilities.

For the infra layer,

The input ports components

• Validate the requests we receive from clients to ensure we receive all necessary data to trigger a business operation.
• Capture the errors from the application layer and transforms them into the errors that need to be returned to the clients making the requests.

The external/outbound adapters

• Validate the parameters they receive from the application components
• Return validation errors and any errors that have occurred from the interaction with the external services (i.e. db errors)

The application layer components

• Do the business logic validations and returns business logic errors. These business logic errors can occur from a combination of data for a specific use case or an invalid state of an entity, for example.
• Could also face errors from their interaction with the domain layer in case there is a failed attempt for a domain action.
• If they interact with an infrastructure service (external adapter), it could also propagate external adapter errors or wrap such errors before they are returned to the input ports callers.

The domain layer

• Is responsible for the domain validations. For example, constructing an entity in the domain layer can have some requirement that, if not met, returns an error.
• Since the domain layer does not have any dependencies on other layers, the errors from this layer occur only from domain validations.

I hope this helps 🙏

[vr-devil]

Thank you, this is the most practical article I have seen so far on using clean architecture in golang projects. The explanation of each layer in the article is in place, and how to realize it is also described clearly.

After reading your article, it is very useful, and I will use it in my project, thank you again.

In addition, I would like to add a layer, which can be called the system layer. The [adapters/app/domain] layer will depend on the system layer. The role of the system layer is mainly to define some system architecture interfaces, realize system-level configuration management, some general mechanisms, some general libraries, and so on.

[deltakroneker]

Well isn't this just a best article on Clean Architecture for Go web servers! Thank you for writing on this topic with very in-depth approach. I am also a Go-beginner and I've been overwhelmed with Go community outright downvoting (without giving scalable alternative) many approaches people make due to the simplistic nature of the language, and I especially love the 'Thoughts' segment where you gave concrete reasoning for this type of package management. I'll be using this for my first Go API pet project as a role model and will give my feedback on how it goes. P.S. Bonus kudos for a fellow climbers' domain :)