{{ item['fields']['Talk-Date'] }}
{{ item['fields']['Name'] }} {{ item['fields']['Location'] }}:
{{ item['fields']['Talk Title'] }}
{{ item['fields']['Talk-Date'] }}
|
![]() ![]() ![]() ![]() |
2019-02 |
2019-01 |
2018-04 |
2018-02 |
2017-12 |
2017-06 |
Your company might want to go for a microservice architecture and apply workflow automation. This sets you in company with a lot of our customers. Typically, you will have questions around: ...
I talk a lot about microservice architectures with “non-Java-folks”, let it be a C# developer, a Node.JS/JavaScript nerd or GoLang enthusiasts. All face the problem that they need an orchestration engine in their microservice architecture — or simply want to leverage workflow, ordering of activities, handling of timeouts, Saga and compensation, or other cool features.
The Open Source BPM platform from Camunda serves these use cases very well. Developer friendliness is one of the key values behind the product ...
The Saga pattern describes how to solve distributed (business) transactions without two-phase-commit as this does not scale in distributed systems. The basic idea is to break the overall transaction into multiple steps or activities. Only the steps internally can be performed in atomic transactions but the overall consistency is taken care of by the Saga. The Saga has the responsibility to either get the overall business transaction completed or to leave the system in a known termination state. So in case of errors a business rollback procedure is applied which occurs by calling compensation steps or activities in reverse order.