3 ms·
Looks very similar to beanstalkd, the only difference I can see is that Faktory comes with a bundled GUI. Is there anything else I'm missing?
by bryanlarsen 9y ago
Looks very similar to beanstalkd, the only difference I can see is that Faktory comes with a bundled GUI. Is there anything else I'm missing?
- aarondf 9y agoFrom the FAK: > Faktory aims to be more feature-rich and better supported. Many of Faktory's OSS competitors are "dead" and no longer supported. I am fortunate enough to have both expertise in background jobs and a business model to support Faktory long-term.
- falcolas 9y agoBackground job systems rarely need extensive support (or, for that matter, a constant stream of features) I've used Gearman for years, to great success. Not saying that Gearman is a better solution, just saying that "better supported" for such a relatively simple tool is not always necessary.
- jsjohnst 9y agoThat it’s written by the same guy behind Sidekiq, a very successful Ruby framework for background jobs.
- switchbak 9y agoI (unfortunately) use beanstalkd, and it seems to be pretty dead, at least on the Java client side. My question is why to we even need a 'background job' system, isn't this just a message broker / queue? RabbitMQ (and friends) can do much of this, no? Maybe I'm missing some of the future features they aim to implement.