Member-only story
Workflow orchestration using Netflix Conductor
Imagine this: You’re building a new insurance platform using microservices architecture, and the customer journey is riddled with complex steps — collecting information, calculating premiums, issuing policies etc. It’s a maze, and keeping track of everything is a nightmare. In a recent project building an insurance platform, we encountered the same challenge. To simplify the management of these intricate processes, we turned to Netflix Conductor(Conductor OSS) as our workflow orchestration engine.
A workflow is a series of tasks describing your business processes and Workflow Orchestration is like having a conductor for your business processes, ensuring each task flows smoothly from one microservice to the next.
In this blog I’ve shared some core concepts of Netflix Conductor, how it works and why it became our choice for an insurance platform.
Why Conductor?
Building an insurance platform involves complex workflows with various steps, decisions, and integrations with multiple microservices. It’s always crucial to orchestrate communication across different microservices and we don’t want to spend our time and effort writing code for orchestrating dozens of microservices. That’s where we’ve found Conductor in rescue.
- Workflow Definition DSL: Conductor…
