Microservices

Learn about the benefits and disadvantages of using Orchestration or Choreography for your microservice architecture.

Learn why Atlassian turned to process orchestration to hyperautomate their tech stack with Camunda and deliver improved customer and employee experiences.

With Amazon SQS, SNS, and Lambda Connectors, as well as Kafka and RabbitMQ Connectors, microservice choreography and orchestration get even closer together.

Microservices are an architectural style that structures an application as a collection of services that are: Highly maintainable and testable Loosely coupled Independently deployable Organized around business capabilities Owned by a small team Conway’s Law states that “any organization that designs a system (defined broadly) will produce a design whose structure is a copy of the organization’s communication structure”. If your organization has multiple teams working on different parts of a larger system, then microservices can serve as a separation of concerns that map an independent, encapsulated service to a specific team. These teams have clear boundaries of responsibility and can deploy on their own schedule. These factors lend themselves to a polyglot approach. What this means is that because...

Dive into our answers for the top-ranked questions from our recent webinar, Looking Back to the Future: 5 Process Automation Trends in 2022.

Outgrowing your monolithic architecture? Explore our best practices and tips on leveraging microservices in your automation program.

In this blog post, we’ll share a few highlights from the microservices orchestration survey that we fielded in July 2018.