Maybe https://gobuffalo.io/en/ is the closest one, 🤔. Source: over 2 years ago

There's nothing like Django for Go, I believe the closest would be Buffalo, typically when building backends in Go you pick and choose a combination of standard library packages and third party packages to build your services. Source: over 2 years ago

These seem to be a way to embed all files to one executeable binary. Similar for Windows is https://github.com/sudachen/Molebox Others: - C/C++ has linker to link all to one binary - CLI/webserver only https://github.com/jart/cosmopolitan like https://redbean.dev . Same exe works on many x64 OS like Windows/macOS/Linux/BSD, it embeds .zip file and can read/write to embedded .zip on the fly. - AppImage... - Source: Hacker News / over 2 years ago

If you want to build a website with Go, first of you don't need nginx or caddy. Go's standard library web server is fantastic. One thing I find with Go is that because it's powerful enough to build a great web server, memory cache, or database, you can solve problems at a lower level. This is something I personally find really fun. If you want a full-on web formwork experience checkout https://gobuffalo.io/en/.... Source: over 2 years ago

It's early days but so far I've quite enjoyed my experience with Buffalo (Golang) framework [1], which mostly copies from Rails. Get Go performance and static typing. Definitely some rough patches, but overall still quite an enjoyable experience (so far). [1] https://gobuffalo.io/en/. - Source: Hacker News / over 2 years ago

My experience of Golang is that dependency injection doesn't really have much benefit. It felt like a square peg in a round hole exercise when my team considered it. The team was almost exclusively Java/Typescript Devs so it was something that we thought we needed but I don't believe we actually missed once we decided to not pursue it. If you are looking at OpenAPI in Golang I can recommend having a look at... - Source: Hacker News / 2 months ago

See https://goa.design/. It automates all the comms stuff, so you just write: 1) a design file showing your functions, 2) an implantation of those functions, and 3) a very generic "main.go" (basically the same for all your services) that decides "how is this exposed over gRPC or REST or other comms?". The rest of the code is generated. Source: 7 months ago

If you really need a framework, you can take a look at Echo or, for a contract-first approach, https://goa.design/. Source: 12 months ago

Few folks in here are (rightly) frustrated with the code generation story and broader tooling support around the OpenAPI standard. I've found a few alternative approaches quite nice to work with: - Use a DSL to describe your service and have it spit out the OpenAPI spec as well as server stubs. In other words, I wouldn't bother writing OpenAPI directly - it's an artifact that is generated at build time. As a Go... - Source: Hacker News / about 1 year ago

One of the biggest issues I see is that you are using the same models for API as you are for the database. That wouldn’t fly in a real work system. And even though your doing simple CRUD I would introduce another layer for business logic. You should never have the Controller calling you database code directly. It never “stays” that simplistic. One of the easiest ways to deal with this is to use... Source: about 1 year ago