rejoiner
rest
| rejoiner | rest | |
|---|---|---|
| 1 | 11 | |
| 3,660 | 316 | |
| 0.1% | 4.4% | |
| 0.0 | 6.6 | |
| 11 months ago | about 2 months ago | |
| Java | Go | |
| Apache License 2.0 | 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.
rejoiner
-
Go stack for REST APIs?
Does google/rejoiner help? This project also seems promising: grpc-graphql-gateway
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.
What are some alternatives?
opentracing-go - OpenTracing API for Go. 🛑 This library is DEPRECATED! https://github.com/opentracing/specification/issues/163
ogen - OpenAPI v3 code generator for go
protobuf-validation - Protobuf validator for Java
openapi-generator - OpenAPI Generator allows generation of API client libraries (SDK generation), server stubs, documentation and configuration automatically given an OpenAPI Spec (v2, v3)
rest-template-go - Template go lang service to showcase REST best practices. Built by the Speakeasy team.
swag - Automatically generate RESTful API documentation with Swagger 2.0 for Go.
grpc-graphql-gateway - A protoc plugin that generates graphql execution code from Protocol Buffers.
Goyave - 🍐 Elegant Golang REST API Framework (v5 release candidate available)
GoSwagger - Swagger 2.0 implementation for go