Never heard of Camel before but had a peek at the docs…

Instead of “Elixir alternative to Camel,” I think the better question to ask is: What are you trying to do in Camel and how can you do that with Elixir instead?

Just from skimming the docs, I see hints of plain Elixir/OTP features, Phoenix, and GenStage/Broadway.

Take this reply with a grain of salt. I am biased. I cringed when I saw “Enterprise Integration Pattern.”

If you have existing dependencies written in Java or other JVM language, or the “enterprisey” aspect is guiding the decision, maybe the BEAM or anything else might be a hard sell.

But it seems there’s room for proposing alternatives, in which case you could compare the many patterns of message-based communication listed in EIPs :: Apache Camel with native/equivalent solutions in the BEAM (as in previous answers in the thread).

Reminds me of that slide comparing BEAM with other stacks, how it replaces a lot of separate components. The legendary talk The Soul of Erlang & Elixir by Saša Jurić https://youtu.be/JvBT4XBdoUE?si=pyKU-_EOHzrTsH1Q&t=36m40s.

Good luck!

Thanks so much for your response. I think this was very useful. I am going to explore and present Elixir/Beam as an alternative.

There’s always JInterface (kind of kidding, I have no experience with it)…

I’d say use Camel as a glue to move messages from external systems to internally managed RabbitMQ and the use Elixir for processing.

This was a feasible approach a few years back and I can only imagine Camel getting better since then.