All Topics
All Topics
Technology
Technology
Design
Design
Programming
Programming
Science
Science
News
News
Gaming
Gaming
Entertainment
Entertainment
Business
Business
Finance
Finance
Sports
Sports
Health
Health
Food
Food
Travel
Travel
Art
Art
Music
Music
Books
Books
Education
Education
Politics
Politics
Personal
Personal
No algorithm. No AI slop. No ads. Just RSS. Pro-human. Indie writers. Real journalism. Open web. Chronological. Hand toasted.

Integrating Elixir and Python Applications Using Oban's Job Queue

By

sorentwo

3mo ago· 6 min readen

Summary

The article discusses using Oban, a job processing library for Elixir, to enable seamless integration between Elixir and Python applications. It addresses the common challenge of needing functionality that exists in Python's mature ecosystem (like machine learning models, PDF rendering, or audio/video tools) while working primarily in Elixir. The solution involves using Oban's PostgreSQL-based job queue to exchange durable jobs between the two languages, allowing teams to collaborate, migrate gradually between languages, or leverage packages from both ecosystems without complex HTTP calls or message queues.

Key quotes

· 4 pulled
What choices lay before you when your Elixir app needs functionality that only exists, or is more mature, in Python?
There are machine learning models, PDF rendering libraries, and audio/video editing tools without an Elixir equivalent (yet).
You could piece together some HTTP calls, or bring in a message queue...but there's a simpler path through Oban.
Whether you're enabling disparate teams to collaborate, gradually migrating from one language to another, or leveraging packages that are lacking in one ecosystem, having a mechanism to transparently exchange durable jobs between Elixir and Python.
Snippet from the RSS feed
Using Oban to seamlessly exchange durable jobs between Elixir and Python applications through a shared PostgreSQL database.

You might also wanna read