opentracing-go
swag
opentracing-go | swag | |
---|---|---|
5 | 36 | |
3,467 | 9,812 | |
- | 1.8% | |
0.0 | 8.1 | |
about 1 year ago | 7 days ago | |
Go | 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.
opentracing-go
- Incomprehensible Performance Issues unraveled with Kubernetes Tracing Tools
-
Distributed Tracing with OpenTelemetry - Part I
OpenTelemetry was born from the merger of two other standards that decided to unify forces instead of competing with each other; these projects were OpenTracing and OpenCensus.
-
Spring WebFlux and gRPC 👋✨💫
Spring web framework Spring WebFlux Reactive REST Services gRPC Java gRPC gRPC-Spring-Boot-Starter gRPC Spring Boot Starter Salesforce Reactive gRPC Salesforce Reactive gRPC Spring Data R2DBC a specification to integrate SQL databases using reactive drivers Zipkin open source, end-to-end distributed tracing Spring Cloud Sleuth autoconfiguration for distributed tracing Prometheus monitoring and alerting Grafana for to compose observability dashboards with everything from Prometheus Kubernetes automating deployment, scaling, and management of containerized applications Docker and docker-compose Helm The package manager for Kubernetes Flywaydb for migrations
-
Learning Go by examples: part 10 - Instrument your Go app with OpenTelemetry and send traces to Jaeger - Distributed Tracing
If you have ever heard of OpenTracing or are used to using it, know that now OpenTracing is deprecated, so it is better to use OpenTelemetry 🙂. If you want to migrate from OpenTracing to OpenTelemetry, an official guide exists.
- Go stack for REST APIs?
swag
-
Seeking Advice on the Best Swagger Generation Approach for REST API
Hey Gophers, I'm exploring Swagger generation for a REST API in Go (using go-chi). Currently, I'm testing https://github.com/swaggo/swag/, but I'm uncertain if it's the optimal solution. What are your thoughts or recommendations?
- Como deixar o Swagger com tema dark mode usando Swaggo e Golang
-
Building RESTful API with Hexagonal Architecture in Go
Swaggo is a tool that creates Swagger documentation for Go APIs. It makes documenting API endpoints easier, helping developers understand and use the API.
-
go-ecommerce-microservices: A practical e-commerce microservices, built with cqrs, event sourcing, vertical slice architecture, event-driven architecture.
Some of the features: - ✅ Using Vertical Slice Architecture as a high level architecture - ✅ Using Event Driven Architecture on top of RabbitMQ Message Broker with a custom [Event Bus](pkg/messaging/bus/) - ✅ Using Event Sourcing in Audit Based services like [Orders Service](services/orders/) - ✅ Using CQRS Pattern and Mediator Patternon top of Go-MediatR library - ✅ Using Dependency Injection and Inversion of Controlon top of uber-go/fx library - ✅ Using RESTFul api with Echo framework and using swagger with swaggo/swag library - ✅ Using Postgres and EventStoreDB to write databases with fully supports transactions(ACID) - ✅ Using MongoDB and Elastic Search for read databases (NOSQL) - ✅ Using OpenTelemetry for collection Distributed Tracing with using Jaeger and Zipkin - ✅ Using OpenTelemetry for collection Metrics with using Prometheus and Grafana - ✅ Using Unit Test for testing small units with mocking dependent classes and using Mockery for mocking dependencies - ✅ Using End2End Test and Integration Test for testing features with all of their real dependeinces using docker containers (cleanup tests) and testcontainers-go library
-
OpenAPI v4 Proposal
[1]https://github.com/swaggo/swag/issues/386
-
[Request] Library Recommendation for Auto Swagger/OpenAPIv3 Documentation
I used this the other day and found it very easy to set up: https://github.com/swaggo/swag
-
Public API documentation. What to use?
I use the fizz for developing my webservices + docs, it's smooth! There is swaggo but I don`t like it because the source code get dirty (lots of comments)
-
Any Working Example for Swagger integartion with golang?
You can use swaggo/swag with code annotations
- Change host in Swagger API
-
Swagger codegen or custom tool
checkout swaggo/swag.
What are some alternatives?
rest-template-go - Template go lang service to showcase REST best practices. Built by the Speakeasy team.
GoSwagger - Swagger 2.0 implementation for go
grpc-spring-boot-starter - Spring Boot starter module for gRPC framework.
gin-swagger - gin middleware to automatically generate RESTful API documentation with Swagger 2.0.
rest - Web services with OpenAPI and JSON Schema done quick in Go
fiber-swagger - fiber middleware to automatically generate RESTful API documentation with Swagger 2.0.
reactive-grpc - Reactive stubs for gRPC
Nginx Proxy Manager - Docker container for managing Nginx proxy hosts with a simple, powerful interface
rejoiner - Generates a unified GraphQL schema from gRPC microservices and other Protobuf sources
echo-swagger - echo middleware to automatically generate RESTful API documentation with Swagger 2.0.
grpc-graphql-gateway - A protoc plugin that generates graphql execution code from Protocol Buffers.
jaeger - CNCF Jaeger, a Distributed Tracing Platform