retry-go
go-simple-mail
| retry-go | go-simple-mail | |
|---|---|---|
| 5 | 5 | |
| 2,223 | 601 | |
| 1.9% | - | |
| 6.2 | 6.0 | |
| 17 days ago | about 1 month 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.
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-simple-mail
-
Microsoft email servers don't support PlainAuth (without modification), but do support LoginAuth. I couldn't find a package to handle it, so I made this one.
This library should support login auth. Does it work with Microsoft email servers?
-
How to get "message-id" sent via net/smtp, SSL?
You can however set a custom message ID, although the standard library doesn't provide an easy way to do this. go-simple-mail to the rescue:
-
Library for sending emails in Go
I like go-simple-mail, it works well for my use case
-
net/smtp issue. "unencrypted connection"
Also, you can use this package https://github.com/xhit/go-simple-mail is easier than standard smtp package
-
Go, NATS, gRPC and PostgreSQL clean architecture microservice with monitoring and tracing 👋
MailHog is good solution for email testing, and for go smtp client here used go-simple-mail.
What are some alternatives?
kafka-go - Kafka library in Go
MailHog - Web and API based SMTP testing
pgx - PostgreSQL driver and toolkit for Go
Gomail - The best way to send emails in Go.
Echo - High performance, minimalist Go web framework
email - Robust and flexible email library 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.
mailyak - An elegant MIME/SMTP email library with support for attachments
grpc-go - The Go language implementation of gRPC. HTTP/2 based RPC
hermes - Golang package that generates clean, responsive HTML e-mails for sending transactional mail
sarama - Sarama is a Go library for Apache Kafka. [Moved to: https://github.com/IBM/sarama]
go-message - ✉️ A streaming Go library for the Internet Message Format and mail messages