The Results Are In! A Review of The 2018 Microservices Orchestration Survey

by Mike Winters on Sep 25 2018 in Microservices.

In this blog post, we’ll share a few highlights from the microservices orchestration survey that we fielded in July 2018. If you’d like to download a report with results, you can do so here.

About the survey: why learn more about microservices architectures?

We at Camunda have been talking to users and customers about how and why to use a workflow engine in a microservices architecture for a long time now. Over the past couple of years, we’ve collected anecdotes and incorporated product feedback into Camunda BPM so that we can better support the use case.

In mid-2017, we started our work on Zeebe, a next-generation workflow engine that can scale to millions of new workflow instances started per second and is built with the microservices orchestration use case at top of mind. And we’ve seen Camunda users give in-depth presentations about how they’re using a workflow engine to orchestrate microservices in the real world.

What we were missing, though, was a broad-reaching set of data that described how members of the Camunda community as a whole were approaching their microservices architectures: the reasons they’re adopting or not adopting microservices, the supporting tools and frameworks they’re using to run their microservices, the benefits they’re reaping and challenges they’re encountering, and more.

It’s not that we ever doubted that there was a real problem that needed solving in the orchestration realm. Beyond our firsthand experience with customers, we saw that some of the earliest adopters of microservices architectures–including Netflix, Uber, Airbnb, and ING–also came to the conclusion that it was to introduce an orchestration layer to monitor and manage long-running business processes that span multiple microservices. All four of these companies have open-sourced the frameworks they built for orchestration and have spoken or written publicly about why microservices orchestration is important to their success.

Of course, we wanted to get more insight into this core orchestration problem in the survey. But we also wanted to go beyond that and fill in some of the blanks around the general patterns and trends in microservices architectures within the Camunda community.

How we carried out the survey

We are thrilled with the feedback we received, and we ended up with 354 responses to the survey. Respondents came from 51 different countries and 12 different industries. So that you know exactly how we managed the survey, here’s a quick rundown of operational details:

Survey highlights

In this post, we’ll mention a few key data points from the survey. We also created a more detailed report with the results that you can download here.

Visibility into cross-microservice processes is a top challenge in microservices architectures

Microservices adoption

Microservices benefits

Microservices challenges

Microservices tools and programming languages

We’d like to extend our thanks to everyone who participated in the survey. We found the input to be very useful, and we hope you did, too.

To learn more, take a look at the full report or read our press release covering the survey results.