Camunda Team Blog

Project Layouts, Journeys and Value Propositions: Monitoring & Orchestrating Your Microservices Landscape using Workflow Automation

Written by Bernd Ruecker on , under Community category.

Back in March, I conducted the webinar: “Monitoring & Orchestrating Your Microservices Landscape using Workflow Automation”. Not only was I overwhelmed by the number of attendees, but we also got a huge list of interesting questions before and, especially, during the webinar. I was able to answer some of these, but ran out of time to answer them all. So I want to answer all open questions in this series of seven blog posts - you can click on the hyperlinks below to navigate to the other entries.

In this blog, we’ll be exploring Camunda Best Practice questions

  1. BPMN & modeling-related questions (6 answers)
  2. Architecture related questions (12)
  3. Stack & technology questions (6)
  4. Camunda product-related questions (5)
  5. Camunda Optimize-specific questions (3)
  6. Questions about best practices (4)
  7. Questions around project layout, journey and value proposition (3)

Q: Where is the best place to start when moving from old legacy monolith workflow systems to Camunda so there is minimum disruption. It depends on so many things. The How to migrate to Camunda whitepaper Can give you some first guidance.

Q: How can you convince monolith users with legacy to move to microservices?

You need to find the current pain points and show how microservices can provide a cure. Companies need to understand the real benefits. You should not apply microservices just because it is hip.

The major benefit is around business agility. Microservices are small, autonomous services that do one small thing very well — and then need to work together. The less they need to communicate with anyone else, the more efficient they can work and the more agile they can be when any change is needed. My favorite quote around that is from Jeff Bezos:

Jeff Bezos

And the metaphor I always use is a three-legged race. If you tie together different teams, so that they need each other to change or deploy anything, you make them all slower. If you cut the bonds, every team can run faster.

race

Of course, this leaves you with the challenge of how these services collaborate — that’s why you inevitably also will stumble over workflows :-)

I searched a bit but did not find a recording where I go exactly over this storyline, probably The Role of Workflows in Microservices gives you at least a glimpse of how I think about that.

: What are the advantages of using Camunda for microservices orchestration?

Following up on the last answer I am convinced that you need orchestration capabilities in your microservices architecture. I discussed this in this webinar, but also for example in Complex event flows in distributed systems.

The second part of this question then is: Why use Camunda instead of any other workflow tool? While I might be a bit biased on this, I am convinced that Camunda has the strongest offering in that space because of the following characteristics:

  • Developer-friendly: No fluff & unrealistic low-code promises, but a great integration into the developers’ world, including tooling and procedures.
  • Highly-scalable: Camunda can back small workflow applications as well as global, mission-critical core business processes. And we help Nasa to get to Mars :-)
  • BPMN/DMN standards-based: We are completely based on well-known and widely adopted standards, that are not only directly executable but also provide visual diagrams, that non-it folk can understand, which brings us to:
  • Business-IT-collaborative (see also BizDevOps — the true value proposition of workflow engines).

Want to learn more?

You can watch Bernd’s webinar here and don’t forget to follow us on Twitter for all of our up-to-the-minute news.