-
Notifications
You must be signed in to change notification settings - Fork 267
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Very interesting article about Clean Architecture. #2
Comments
Thanks for the pointer. I just read the article and the code in the repo. I don't fully agree with some of its designs.
I do agree with what the author says in the "The only rules you need to know" section. While designing and implementing this project, I researched nearly every repo that claims implementing the clean architecture. I found most of them try to implement the architecture in a very dogmatic way, and the end result is that they become extremely complex and thus receive little interest from practical adoption. |
Yes I agree, your groupping structure is best for me. But some features from that project are useful for my opinion. |
Good to hear that. Could you share what are useful and how you will use it? |
Yes! Now I do refactoring all my actual projects to this new starter. I split it into microservices. When I will get some statistic I will send your my feedback.) |
https://github.com/go-kit/kit/tree/master/examples/shipping also good reference. I like how they compose an existing service into something called instrumenting service for metrics or something. Good job everyone :) |
Hi, Qiang! I found nice article about Clean Architecture in Golang. Did you read it?
I like that the presenter extracted from Use Case layer. In our starter it hardcoded in service. And good solution, that this example fully independent from routing library.
And good, that controllers are stay clean.
Thanks!
https://medium.com/manato/clean-architecture-with-go-bce409427d31
The text was updated successfully, but these errors were encountered: