goa VS Gin Gonic

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: 4 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: 10 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 / 11 months 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: 11 months ago

I left PHP for Go. - with http://sqlc.dev I don't have to write ORM or model code anymore. - with http://goa.design I can have well-documented API's that any team can generate a client for in any language. It also generates the HTTP JSON and gRPC servers for me so I can focus on my logic. - with https://github.com/99designs/gqlgen project to make it super simple to use a durable, always backed-up SQLite database... - Source: Hacker News / 11 months ago

Most golang backends I've seen meanwhile use or switched to using the "gin" framework to build their APIs. A lot of them also have conventions for the frontend, where the assets usually are stored in /public, so they can be go:embed later as an embed.FS instance into the binary. Having said that, there's plenty of examples on github. I'd recommend to take a look at bigger projects or templates and understand how... - Source: Hacker News / 3 months ago

Excellent Performance: Sponge is built on the gin framework, providing outstanding performance for web service development. - Source: dev.to / 3 months ago

In this blog, we will delve into the fascinating realm of handling images in a Golang application, leveraging the power of the Gin framework for RESTful API development, MongoDB as a robust NoSQL database, and the mongo-driver library for seamless interaction with MongoDB. To store images efficiently, we'll explore the intricacies of GridFS, a specification within MongoDB for storing large files as separate chunks. - Source: dev.to / 4 months ago

For building the RESTful Point of Sale service API, I've considered and selected a combination of technologies that would work seamlessly together. For handling HTTP requests and responses, using the Gin HTTP web framework would make sense because I think it seems complete and popular among Go community too. To ensure data integrity and persistence, I'm using PostgreSQL database with pgx as the database driver,... - Source: dev.to / 7 months ago

I have created an application with Go in Gin-Gonic. In my frontend (Nuxt3/TypeScript) I always get a CORS error:. Source: 8 months ago