Hi @shashi, what do you mean by “reactive microservices”?
Take a look at these blog posts:
Zeebe itself is written using the Actor model - see: https://github.com/zeebe-io/zeebe/issues/635
You can write your task workers using Akka. But again, much of what Akka brings to the table are solutions for classes of problems that Zeebe side-steps for you architecturally.
How you pitch this depends also on what your existing tech stack / dev team looks like.
If I were pitching it to a company with Akka already implemented, then for sure I’d be pitching Zeebe + Akka. If there were no existing Akka investment, however, I would be making a table of scenarios that we needed to address with the system, and then sketching out the solutions to each one using various techs.
With Akka you get a programming model for distributed concurrent systems, and libraries that implement the primitives. Then you have to roll the whole thing.
With Zeebe you get a God Service written using the actor model that is light-weight and scalable, that allows incredible flexibility in your system design, and provides you with executable BPMN diagrams that document exactly how your system works, along with powerful operational monitoring.
It’s basically a large chunk of an Akka system pre-written, with the strongly-held opinion that there should not only be a God Service, but a Come-to-Mt-Olympus service that materialises knowledge of the architecture and centralizes running state.