- how does it compare to bullmq and celery?
Oban, the job processing framework from Elixir, has come to Python
81–90 of 107 posts
Re: Oban, the job processing framework from Elixir, has come to Python
#82This is something my company has been considering for a while. We've been using celery and it's not great. It gets the job done but it has its issue. I've never heard of Oban until now and the one we've considered was Temporal but that feels so much more than what we need. I like how light Oban is. Does anyone have experience with both and is able to give a quick comparison? Thanks!
I'm just coming back to web/API development Python after 7-8 years working on distributed systems in Go. I just built a Django+Celery MVP given what I knew from 2017 but I see a lot of "hate" towards Celery online these days. What issues have you run into with Celery? Has it gotten less reliable? harder to work with?
Most Django projects just need a basic way to execute timed and background tasks. Celery requires seperate containers or nodes, which complicates things unnecessarily. Django 6.0 luckily has tasks framework -- which is backported to earlier django versions has well, which can use the database. https://docs.djangoproject.com/en/6.0/topics/tasks/
Re: Oban, the job processing framework from Elixir, has come to Python
#83Is this a good alternative to celery? Can we use it with the Django Task Framework?
Re: Oban, the job processing framework from Elixir, has come to Python
#84I don't know how I feel about free open source version and then a commercial version that locks features. Something inside me prevents me from even trying such software. Logically I'd say I support the model because open source needs to be sustainable and we need good quality developer tools and software but when it comes to adoption, I find myself reaching for purely open source projects. I think it has to do with f…
Their business model is similar to Sidekiq in this regard. (Which we have happily paid for, for years.)
Re: Oban, the job processing framework from Elixir, has come to Python
#85Any plans for Typescript?
Re: Oban, the job processing framework from Elixir, has come to Python
#86Its not clear to me why youd need a tool to do this. Arent transactions and queue (say with celery) easy to write?
Re: Oban, the job processing framework from Elixir, has come to Python
#87When I hear Oban, the first thing that comes to mind is a great 14yo scotch :D
Re: Oban, the job processing framework from Elixir, has come to Python
#88Its not clear to me why youd need a tool to do this. Arent transactions and queue (say with celery) easy to write?
Not necessarily easy to do performantly, scalably and well. Oban has been doing this in Elixir at real scale for a decent while now.
Why do you need a tool? Well. You say celery. I am inclined to say Oban. And I'd say both are tools.
Re: Oban, the job processing framework from Elixir, has come to Python
#89I recommend [Celery]( https://docs.celeryq.dev/en/stable/ ). Celery is a simple, flexible, and reliable distributed system to process vast amounts of messages, while providing operations with the tools required to maintain such a system. BTW its free.
I believe the OSS part of this oban library covers a lot of the celery feature set and is free as well. You can run multiple nodes and knock yourself out without needing more infra than the existing postgres.
Oban has been a free and OSS project in Elixir for ages. There are some more advanced bits that are paid and that sustains the people that make it.
If you like Celery. Great. This is a different take. I didn't enjoy celery last I needed it but never got super familiar.
Re: Oban, the job processing framework from Elixir, has come to Python
#90I don’t like that the oss version is gimped compared to the pro one.