rest
goa
rest | goa | |
---|---|---|
11 | 41 | |
314 | 5,465 | |
3.8% | 0.5% | |
6.6 | 9.3 | |
about 1 month ago | 10 days ago | |
Go | Go | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
rest
- I write HTTP services in Go after 13 years (Mat Ryer, 2024)
-
Create Production-Ready SDKs with Goa
Swaggest Rest can generate OpenAPI definitions from Go code, but it's not as comprehensive as Goa and does not support gRPC.
-
[Request] Library Recommendation for Auto Swagger/OpenAPIv3 Documentation
This is what I use: https://github.com/swaggest/rest
-
FastAPI Replacement - especially with openapi
This has been the best implementation of the use case interactor I’ve seen and it outputs spec 3: https://github.com/swaggest/rest
-
What is the recommended/preferred web architecture for web applications / services written in Go?
Other times you might need a JSON REST API to generate OpenAPI docs code-first… for that I’m a fan of Swaggest REST. REST through clean arch.
- Gorilla toolkit maintainers are stepping down and have been looking for new maintainers. The project could otherwise be archived.
-
Go stack for REST APIs?
For full code-first OpenAPI v3 REST, I’ve been using https://github.com/swaggest/rest and I like it.
-
Best golang framework for microservice
For anything that needs OpenAPI docs, I’ve honestly found https://github.com/swaggest/rest pretty awesome. It’s basically just doc generation on top of Chi, but it does a lot of stuff right.
-
Do you use frameworks?
I used Echo for a lot of stuff (and it was easy to work with), but recently OpenAPI 3 has been a requirement, so I've switched to https://github.com/swaggest/rest
-
Do you use swagger to generate backends?
I've tried go-swagger comments to instrument existing code, but wasn't quite satisfied due to magical nature and error friendliness of those comments. So I decided to implement first-class OpenAPI generation on top of self-documenting action handlers: https://github.com/swaggest/rest/blob/master/_examples/basic/main.go. Schemas are generated from request and response structures using reflection and field tags.
goa
-
IBM to Acquire HashiCorp, Inc
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 https://goa.design/. It's a DSL that generates OpenAPI specs and provides an implementation of the endpoints described. Can also generate gRPC from the same definitions.
We found this removed the need to write almost all of the API layer and a lot of the associated validation. We found the generated code including the server element to be production ready from the get go.
-
Microservices communication
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.
-
Create Production-Ready SDKs with Goa
Perhaps the easiest way to find out how to do something (especially when using Meta) is to search the test cases when you have cloned the source code.
-
Which is the best framework to create web apps with go?
If you really need a framework, you can take a look at Echo or, for a contract-first approach, https://goa.design/
-
OpenAPI v4 Proposal
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 user, I quite like Goa (https://goa.design/) but there are others shared in here like TypeSpec.
- There are situations where sticking a backend-for-frontend (BFF) in front of APIs can yield great productivity boosts. For example, in the past we built a thin GraphQL proxy that calls out to a poorly structured REST API. Integrating with that was much more convenient. Most recently, I've been playing with a BFF built with tRPC (https://trpc.io/) which calls out to a REST API. It seemed to provide an even better experience if you use TypeScript on the front-end and in the BFF. It does not have a codegen step and I was really pleased with how fast I could iterate with it - granted it was a toy project.
-
Beginner-friendly API made with Go following hexagonal architecture.
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 Goa. https://goa.design/ It takes care of generating your API models and it creates the Interfaces to implement for your business logic. Furthermore it creates OpenAPI documentation (something missing in this design that is a must for commercial development).
-
Go with PHP
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 I can define GraphQL revolvers that play well with sqlc (any RDBMS) or I can use a key-value store.
- speaking of key-value stores, Go allows them to be embedded! Even SQLite now has the https://litestream.io/ project to make it super simple to use a durable, always backed-up SQLite database even in a serverless context.
Go is faster, uses less memory, and has really-well designed stdlib without all the bugs I used to face trying to use the PHP stdlib.
-
Do you really need microservices?
Goa and Kong are some of the best frameworks to develop and deploy microservices. They provide features such as out-of-the-box support for service discovery, routing and authentication that make it easier to build more complex applications. There are also newer architectural frameworks with less steep learning curves like GPTDeploy that lets you build and deploy microservices with a single command.
-
Dumb question about APIs, Mux and Go
Or the one we use at work: https://goa.design/ Goa does a lot more and maybe more than you need. We use it as it can generate both REST and gRPC as well as API models and OpenAPI documentation (JSON and YAML).
- Why is gin so popular?
What are some alternatives?
ogen - OpenAPI v3 code generator for go
Gin - Gin is a HTTP web framework written in Go (Golang). It features a Martini-like API with much better performance -- up to 40 times faster. If you need smashing performance, get yourself some Gin.
openapi-generator - OpenAPI Generator allows generation of API client libraries (SDK generation), server stubs, documentation and configuration automatically given an OpenAPI Spec (v2, v3)
go-kit - A standard library for microservices.
swag - Automatically generate RESTful API documentation with Swagger 2.0 for Go.
GoSwagger - Swagger 2.0 implementation for go
opentracing-go - OpenTracing API for Go. 🛑 This library is DEPRECATED! https://github.com/opentracing/specification/issues/163
oapi-codegen - Generate Go client and server boilerplate from OpenAPI 3 specifications
Goyave - 🍐 Elegant Golang REST API Framework (v5 release candidate available)
Echo - High performance, minimalist Go web framework
gqlgen - go generate based graphql server library