go-clean-arch VS service

I'm working on a project that makes use of Hexagonal Architecture to keep things loosely coupled and I learned golang recently. So, I would recommend you to check out Go clean arch, I think you can a learn a lot from it.

Try this

It will be good to have a look at the Go (Golang) Clean Architecture based on Uncle Bob's Clean Architecture https://github.com/bxcodec/go-clean-arch

Has anyone come across any Golang repo like go-clean-arch which uses elasticsearch? As I am a beginner and wanted to have a bit of practice of building microservice using Go with Elasticsearch.

Thanks, everyone. I am able to understand a few things using go-elasticsearch. Though Olivere/elastic is simpler, it is not future-proof. I just wanted a repository similar to cleanarchitecture which uses elasticsearch, on the top of which I can practice. Please provide a link here if anyone has come across such a repo.

View on GitHub

https://threedots.tech/post/introducing-clean-architecture/ https://github.com/bxcodec/go-clean-arch

Ultimate Service was useful for me. None of the "backend" concepts were new, but you get to see how Bill would layout/design an API-based service. If you're experienced you'll notice the opinionated choices he makes, and I found myself saying "Nah, I'm not sure I'd do it like that". I appreciated its use of Kubernetes and KIND as I'd never played with them before. How he uses Docker to spin up a DB instance for tests is pretty cool. There's a lot of copy & paste as you code along with him (you copy from the "finished project" and paste into your work in progress). The full example project is online at https://github.com/ardanlabs/service. You won't write all that code, and this version is newer than the one I did, but it gives you an idea of what you might learn.

So what can you do insted? For testing databases, setup a docker instance for tests (e.g. like in https://github.com/ardanlabs/service), or start an embedded-postgres daemon (see https://github.com/fergusstrange/embedded-postgres). For communication with external APIs, just pass the http.Client (either in context.Context or as a field on the struct). Then in tests, you can override the http.Client.Transport func.

Take a look at https://github.com/ardanlabs/service from Bill Kennedy. You can probably simplify the structure a bit since your project is minimal, but that repo is gold.

Checkout https://github.com/ardanlabs/service for inporation. Tip: try to avoid creating a service package with all services, a domain package with all domain structs, etc.

Or go through this repo https://github.com/ardanlabs/service

I've seen this handler modification and wrapping pattern in Ardan Labs' service repository. https://github.com/ardanlabs/service/tree/master/foundation/web

https://github.com/ardanlabs/service This is something which I really like and has taken into account a lot of engineering decisions.