Clean design pattern

• UserService

  3 3 6.8 Go

  This is a demonstration of a user microservice with MongoDB as the datastore

for a restful service, DELETE should be the same URL for a GET or a PUT /users/blue_boro_gopher vs as a query parameter

• bootstrap-echo-openapi-docker

  1 1 1.8 Go

  Bootstrap repo for echo, openAPI and Docker

It’s not exactly what you’re looking at, but if you are interested in how to make echo, OpenAPI and docker work together for an API then I found this helpful.

• InfluxDB

  www.influxdata.com sponsored

  Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

  

• saving-goals-go

  1 6 1.8 Go

  Example Event-Sourced microservice using https://github.com/eventually-rs/eventually-go (by get-eventually)

  

I didn't mean "don't use dependency injection/inversion" (you SHOULD definitely use it), but rather "don't use dependency injection FRAMEWORKS". Initialize the dependencies and passing them around by hand should be fine in 99.99% of the cases. If it starts getting hairy, you can use some simple functions that perform part of the initialization. Do everything in the `main()` but comment different chunks of the initialization (e.g. https://github.com/get-eventually/saving-goals-go/blob/main/cmd/saving-goals-api/main.go)

Suggest a related project