Communication Between Loosely Coupled Microservices
In our recent webinar titled “Communication Between Loosely Coupled Microservices” we got a lot of great questions and because of the limited time some were left unanswered. As community questions are really important to me I want to follow my tradition to answer remaining questions in a blog post (as I have for example also done roughly a year ago in “Webinar FAQ for Monitoring & Orchestrating Your Microservices Landscape using Workflow Automation”). What Was The Webinar About? You can find the slides (here) and recording (here) online. The webinar covered different styles of communication. This was explained by looking at how ordering food works: Synchronous blocking: A call uses a synchronous protocol, like HTTP, and blocks for the result. This is you, calling a pizza...
Stateful Orchestration (or, Why Your Microservices Application Needs a Brain)
When checking in for a flight online, normal people hope that everything works the way it’s supposed to. That usually means no error messages, and at the end of the process, getting a boarding pass in your selected format. We at Camunda, however, are not “normal people”. A problem during check-in is a bit of a thrill for us because it gives us a peek into how a company handles software failures in a high-traffic application. We never know exactly what’s happening under the hood, of course, but we like to speculate.
Enterprise Platform for Workflow and Decision Automation