Welcome to goilerplate Discussions!

[resotto]

👋 Welcome!

We’re using Discussions as a place to connect with other members of our community. We hope that you:

• Ask questions you’re wondering about.
• Share ideas.
• Engage with other community members.
• Welcome others and are open-minded. Remember that this is a community we
  build together 💪.

To get started, comment below with an introduction of yourself and tell us about what you do with this community.

[resotto]

remaining topic （I'll copy some of main discussion there to this comment later）
#2

[IzioDev]

Hey there,
Thanks you for your time investment in this project. I totally learnt something cool today and will give it a real long try.

However, I feel like this architecture is verbose, at least this Golang implementation. This verbosity abstract layers and define contracts between components (layers), hence facilitate testing and allow us to change the postgres implementation into graphql for example, without changing all the code but only the adapter if I understood well.

So I would add some kind of ⚠️ somewhere to say that for PoC or small projects that don't care about maintainability first, that this probably is an overkilled architecture.

This is just my point of view right now, and it probably will change while seriously try this architecture implementation in Golang.

Thanks again for all the time you spend making a clean open source boilerplate of good architecture implementation.

PS: If you guys have any tool to make layer generation automatically (schematics), like mycli generate entity, please let me know!