Oban, the job processing framework from Elixir, has come to Python

Python just got Elixir’s cult‑favorite job runner, Oban—and the crowd went instantly split. Celery veterans (that’s the popular Python task tool) shuffled in with “it works, but ouch,” while one dev joked they’re ready to swap their celery for something less wilted. Another camp shouted that this database‑first approach is the glow‑up they’ve been begging for: keep your tasks in Postgres, not a separate cache, and stop babysitting extra infrastructure.

Then Sidekiq’s own creator, mperham, dropped in like a surprise guest star, noting Oban’s roots in Sidekiq and plugging his cross‑language alternative, Faktory. Cue the framework family drama. Meanwhile, workflow‑tool skeptics said Temporal is “too much hammer for our nails,” making Oban’s “lighter” vibe sound very attractive.

But the real spice? Open‑core angst. Oban’s free version is fine for small apps, while Pro unlocks the fast lane—true parallelism, bulk operations, smarter recoveries. Some cheered the sustainability, others side‑eyed the paywall. One commenter summed it up: “I support it in theory, but I hesitate in practice.” Over in the peanut gallery, Elixir diehards begged for the reverse migration: “Why not bring Python’s data pipelines to Elixir?” Translation: if Elixir’s the concurrency king, why is Python getting the party? Between database‑vs‑Redis debates, “Celery detox” jokes, and a Sidekiq shout‑out, Oban’s Python debut is less tech launch, more reality‑TV reunion—with code.