That would indeed have been better, but the product itself is pretty much à about handling and processing events, so...

It feels like having the architecture not be event-driven when the whole product is about dealing with events would be the same as going the event-driven architecture route for, let's say, a knowledge-sharing SaaS

But I will definitely keep spark in mind for the future, thank you :-)