I agree that in many areas there often is not much in-between "roll yourself in-memory" and "enterprise grade maxed out scalability focus".
But, for sure, having your own SDKs has advantages too - you don't depend on anyone else's protocol decisions, have less dependency, eyc.
Btw, the first time I saw one company use another company's SDK, which I really liked, was in 2023, when DeepSeek used OpenAI's SDK and still think it was brilliant.
Save yourself the headache of people not reading this and just disable pull requests in the repo settings
Re inspiration: no direct inspiration really, just needed this tool myself for my own projects. But I guess this project as my engineering taste was kind of influenced/validated by bright minds like Richard Hipp, Joe Armstrong, and Derek Sivers
If so should we also consider PostgreSQL overengineered?
It's a shame OP decided to use Elixir as base, many ecosystems don't have mature task queues (e.g. for Rust I had to roll my own: simple_queue) so the space IMO would be more welcoming.
On OTP doubt anything can even make a dent in Oban user base.
as an answer: tare actually two ways to run it. As a standalone binary, it's one process you run(you can easily run it via docker too) on its own(which speaks on Redis protocol over TCP) - and any language connects to it like a Redis server.
Or, if you're on Elixir, you can skip the separate process entirely and add it directly to your app's supervision tree - it runs inside your own app's process, no network hop, just function calls.