Building an idempotent email API with River unique jobs - River blog

Atomic, transaction-safe job queueing for Go applications. Backed by PostgreSQL and built to scale.

I'm in an internal struggle with building things now.

Do I either use #golang, #nats, #htmx, #templ, #postgres, #riverqueue, and bask in the greatness of fitting each to perfection? ๐Ÿค”

Or do I use #elixir, #phoenix, #postgres, #oban, and finish building the app in a day? ๐Ÿ˜…

Job queue systems are a must if you want to handle errors. In #elixir, this is #oban that is your goto.

Now in #GoLang, there's #riverqueue. ๐Ÿ˜… I'm already looking how to replace backbone of services. ๐Ÿ˜‰

So many times I wished I had a solution like this in go. Instead of having rebuild a half bake version every other project. ๐Ÿซ 

https://riverqueue.com/

River - Fast, reliable background jobs in Go

Atomic, transaction-safe job queueing for Go applications. Backed by PostgreSQL and built to scale.