Hi Sdrolias. This is just one example architecture for microservices. It's certainly a nice idea to use external tasks when you want to use the engine on its own as a standalone orchestration server. Here Bernd is showing an architecture where Camunda is not an architectural component, but instead an embedded component as part of a service. Both approaches are equally relevant!
Very insightful. Thank You!
Thanks for a great exmplanation!
Great talk!
At the end, the Bernd Rucker is not suggesting for microservices, the use of Camunda with external tasks. What is the reasons behind this?
Hi Sdrolias.
This is just one example architecture for microservices. It's certainly a nice idea to use external tasks when you want to use the engine on its own as a standalone orchestration server. Here Bernd is showing an architecture where Camunda is not an architectural component, but instead an embedded component as part of a service. Both approaches are equally relevant!