3 ms·
The only flaw here seems to be a lack of use-case... why not just add an HTTP API to Sidekiq instead, if it doesn't already have it? That way the value of the q
by manigandham 9y ago
The only flaw here seems to be a lack of use-case... why not just add an HTTP API to Sidekiq instead, if it doesn't already have it? That way the value of the queue logic and semantics can be offered to any external client.
- mperham 9y agoSidekiq is not a server, it's a Ruby worker process. Redis is the server and I can't build a fast, easy to use embedded queue system on top of Redis.
- manigandham 9y agoCan't Sidekiq just run as a standalone process? It can take a connection string to use existing Redis/RDBMS with option to use embedded server maybe. You can just package it with Redis in a container too. Although to be honest, the basics of a work queue are well covered now with the evolution of cloud services and other databases and message systems.
- mperham 9y agoSidekiq is Ruby only. That won't support one of my key goals with Faktory: polyglot. Background jobs can benefit applications written in many languages. There's many different tools and many different users. No one choice is appropriate for all. I hope some people find Faktory useful.
- deleted 9y ago[deleted]