retry-go
Go-Kafka-gRPC-MongoDB-microservice
Our great sponsors
| retry-go | Go-Kafka-gRPC-MongoDB-microservice | |
|---|---|---|
| 5 | 1 | |
| 2,202 | 145 | |
| 2.9% | - | |
| 5.7 | 0.0 | |
| 5 days ago | about 3 years ago | |
| Go | Go | |
| 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.
retry-go
-
Retry operations with constant, delays and exponential backoff strategies
Why this instead of https://github.com/avast/retry-go or https://github.com/cenkalti/backoff ?
- Network Error Handling
-
retry package for golang
What is that advantage of your package compared to other ones like https://github.com/avast/retry-go?
-
Go, NATS, gRPC and PostgreSQL clean architecture microservice with monitoring and tracing 👋
processCreateEmail handling create email events, it's start tracing span, increase metrics counters, then unmarshal message data, and call usecase create method, if it fails, we retry for 3 times using retry-go, if it still fails, we check is the current message redelivered and if redelivery count > maxRedeliveryCount(it's up to your business logic, here is 3 times limit), handling error cases can be very different and depends on your service business logic, in this example used Dead Letter Queue approach.
-
Go, Kafka, gRPC and MongoDB microservice with metrics and tracing 👋
Workers validate message body then call usecase, if it's returns error, try for retry, good library for retry is retry-go, if again fails, publish error message to very simple Dead Letter Queue as i said, didn't implement here any interesting business logic, so in real production we have to handle error cases in the better way. And after message success processed commit it.
Go-Kafka-gRPC-MongoDB-microservice
-
Go, Kafka, gRPC and MongoDB microservice with metrics and tracing 👋
On top layer of our app handling, logging errors and process metrics for Prometheus. Repository with the source code and list of all used tools u can find here 👨💻 :) I hope this article is usefully and helpfully, I'll be happy to receive any feedbacks or questions :)
What are some alternatives?
kafka-go - Kafka library in Go
go-clean-architecture-web-application-boilerplate - A web application boilerplate built with go and clean architecture.
pgx - PostgreSQL driver and toolkit for Go
spring-petclinic-microservices - Distributed version of Spring Petclinic built with Spring Cloud
Echo - High performance, minimalist Go web framework
goharvest - Transactional outbox harvester for Postgres → Kafka, written in 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.
csgo_exporter - A Prometheus exporter for Counter-Strike: Global Offensive.
grpc-go - The Go language implementation of gRPC. HTTP/2 based RPC
Zenko - Zenko is the open source multi-cloud data controller: own and keep control of your data on any cloud.
sarama - Sarama is a Go library for Apache Kafka. [Moved to: https://github.com/IBM/sarama]