ratus VS go-events

The Go ecosystem has many brilliant distributed task queue libraries, but sometimes we still have to settle for some bloated cross-platform solution in order to work with components written in other languages. To solve this problem, we created Ratus, which is a service, not a library. It translated concepts of distributed task queues into a set of resources that conform to REST principles and provides an easy-to-use HTTP API. Ratus is implemented in Go, and comes with a Go client library. Asynchronous task queues are typically used for long-running background tasks, so the overhead of the HTTP API is not significant compared to the time spent by the tasks themselves. On the other hand, the HTTP-based RESTful API can be easily accessed by all languages without using dedicated client libraries.

To solve this problem, we created Ratus, which is a service, not a library. It translated concepts of distributed task queues into a set of resources that conform to REST principles and provides an easy-to-use HTTP API. Ratus is implemented in Go, and comes with a Go client library. The current default storage engine is MongoDB (in-memory store coming soon), we will also try to integrate existing Go task queue libraries.

I've been working on https://github.com/hyperonym/ratus which is a RESTful asynchronous task queue server, it also comes with a Go client library.

For libraries I use at work, cmap has a v2 using generics. I think that's a fairly widely used library. The events library we use is updated, but not released. When I get a chance, planning on looking on moving to hooks, which does have released generics support.

Looks interesting. I was actually considering writing something like this, as we use https://github.com/kataras/go-events, which is similar, but doesn't have released generics support yet. I'll give this a try before trying to bake my own.