faktory

I wrote Sidekiq, which Oban is based on. Congratulations to Shannon and Parker on shipping this! I had to make this same decision years ago: do I focus on Ruby or do I bring Sidekiq to other languages? What I realized is that I couldn't be an expert in every language, Sidekiq.js, Sidekiq.py, etc. I decided to go a different direction and built Faktory[0] instead, which flips the architecture and provides a central server which knows how to implement the queue lifecycle internally. The language-specific clients become much simpler and can be maintained by the open source community for each language, e.g. faktory-rs[1]. The drawback is that Faktory is not focused on any one community and it's hard for me to provide idiomatic examples in a given language. It's a different direction but by focusing on a single community, you may have better o

Guessing the Go experience is largely from faktory https://github.com/contribsys/faktory But I dunno you can just go ask him about it, assuming he still does those Friday morning “happy hour” calls :)

> I think the experience of code rot is universal and increases with the amount of dependencies you have. This is true but there's also a factor from the language/framework in use. Node is especially bad because of it generates huge package dependency trees. Go is especially good because of the large stdlib (which I use to minimize deps in https://github.com/contribsys/faktory) and excellent backwards compatibility.

This is a fairly old article, but this has become a very common pattern. For 90% of projects that just need a task queue for sending email or generating reports, you're not going to be doing millions of messages a second and anything that simplifies your stack is worth looking at. I've used these patterns so often to work around issues encountered with Celery that I've split them into their own framework, https://github.com/TkTech/chancy (feedback appreciated ;) There are lots of these, several of which are commercial ventures so there's definite interest behind it: https://worker.graphile.org/ (Node.js) https://riverqueue.com/ (Go) https://github.com/acaloiaro/neoq (Go) https://github.com/contribsys/faktory (Go) https://github.com/sorentwo/oban (Elixir) https://github.com/procrastinate-org/procrastinate (Python)

As mentioned, there are a plethora of queuing systems that have cross platform clients. If you’re interested specifically in a background job system, you may want to check out Faktory. It’s Mike Perham’s language-agnostic follow-up to Sidekiq. https://github.com/contribsys/faktory

Thanks, looks potentially interesting: https://github.com/contribsys/faktory And it's written in Go. :)

Mike Perham (the sidekiq maintainer) also maintains the less well known faktory[0] which is language agnostic and has runners for both Ruby and Python [0] https://github.com/contribsys/faktory

Zen and the Art of Motorcycle Maintenance's entire thesis is "What is Quality?" How do you define it? How does it come about? You can still get software quality but you have to be willing to devote time and effort to it. The binary for my modern, commercial background job engine written in Go, Faktory, is 5MB in size. https://github.com/contribsys/faktory/releases/tag/v1.8.0 I know when I see an iOS app that is 5-10MB in size, I know it was crafted by someone who cares. Overcast being one example.

I got into it before Oban was ever released. However, it seems like a solid solution. I've looked at Faktory as another great option as well: https://github.com/contribsys/faktory/

Here are a few interesting pieces in Rails specifically: - https://github.com/hopsoft/stimulus_reflex is inspired by Phoenix LiveView and is getting a bit of traction around me - https://github.com/hopsoft/cable_ready is a companion project - https://github.com/discourse/message_bus by Sam Saffron from Discourse is a nice way to implement live updates too, quite easily (video demo at https://twitter.com/thibaut_barrere/status/12565974431075860...) - https://lamby.custominktech.com is a Rails + AWS Lambda integration which is also gaining a bit of traction I also see interesting stuff in Ruby more generally these days: - my own https://www.kiba-etl.org (data processing framework) is growing nicely - https://sidekiq.org is very solid and used in most Rails app I've seen - https://github.com/contribsys/faktory allows interop-jobs (e.g. creat

Most job systems like Celery or Sidekiq are language-specific. If you are looking for background jobs for any language, check out Faktory. More advanced features like queue throttling and complex job workflows are available. https://github.com/contribsys/faktory/wiki

I'm the author of Sidekiq, which supports first-class scheduled jobs. It's designed for Ruby apps. https://sidekiq.org I'm also the author of Faktory, which supports first-class scheduled jobs and is designed for applications in any language. https://github.com/contribsys/faktory Both are open source and both have commercial support so they will be maintained for years to come.