If you have used Camunda or Temporal, you know what a process engine gives you: sagas, human tasks, timers, an operations console, versioned processes. EventConductor gives you the same, MIT-licensed, as a library inside your Spring Boot app instead of a platform to run beside it — and it fixes a few things we always missed.
A three-step process is mostly plumbing
Take a hotel booking. On a whiteboard it is three steps: a manager approves it, each room is booked at the hotel, the guest is told.
In production you also need:
Undo what was booked , but only if the guest decides to cancel when one room turns out to be sold out.
Retry without booking twice when the hotel's API times out.
Survive a restart halfway , with two rooms booked and one pending.
Wait days for a person , with reminders and an escalation.
Change the process while bookings are still running.
Answer "where is booking 123?" without reading logs.
Written by hand, that is most of the code, and almost none of it is about hotels.…