I’m currently evaluating workflow and orchestration tools, and I’m particularly interested in understanding the differences between Camunda 8 and Temporal. While I’m aware of the BPMN capabilities in Camunda 8, I’m looking for insights into other aspects where these two platforms might vary.
Could anyone please share their experiences or knowledge regarding features, performance, scalability, integration capabilities, or any other significant aspects that distinguish Camunda 8 from Temporal?
I don’t know Temporal too well, but on what I’ve seen, they’re focusing on a specific subset of Process Orchestration. While Camunda aims to create features that allow for end-to-end process orchestration Temporal is only interested in the microservices part of the puzzle.
Camunda of course can orchestrate microservices, and it’s as a core use-case it’s too narrow a focus for true end-to-end process orchestration. For that you need the ability to include more diverse end points (e.g. Front-End Applicatoins, RPA bots, Kafka, legacy systems… etc).
So with those concepts in mind, Camunda has a bunch of additional features go beyond catering for a purely micro-service-centric* mindset. BPMN is of course a big part of that. There’s also features for building reusable services and being able to share those across a teams or throughout company. Making it easier to maintain those services and to build processes that want to use those services.
Temporal (probably) requires a software developer to understand, explain, maintain and build it’s processes. While Camunda expands the roles that can be involved. Citizen developers can build processes, Developers can build or connect the services to be orchestrated and DevOp folk and Analysts have a visual representation of what’s really happening in the process for either fixing issues or simply reporting on KPIs and metrics.
Little bit of a ramble there, but I hope it helps.
*Is that actually a word 