Orchestration Patterns for Microservices with Messaging by RabbitMQ

April 18, 2017
Companies looking to speed up their software development are adopting microservices architectures (MSA). Building applications as groups of smaller components with fewer dependencies helps companies such as Comcast, Capital One, Uber, and Netflix deliver more frequent releases and thus innovate faster. An important consideration in adopting an MSA is deciding how individual services should communicate between each other. Adding a message queue such as RabbitMQ to handle interservice messages can improve communication by: - Simplifying our services so they only need to know how to talk to the messenger service. - Abstracting communication by having the messenger service handle sophisticated orchestration patterns. - Scaling message throughput by increasing the cluster size of the messenger service. In this webinar we'll discuss: - Requirements for communicating between microservices - Typical messaging patterns in microservice architectures - Use cases where RabbitMQ shines - How to use the RabbitMQ service for Pivotal Cloud Foundry to deploy and run your applications We’ll also demonstrate how to deploy RabbitMQ in Pivotal Cloud Foundry, and how to incorporate it in microservices-based applications. Presenters: Greg Chase, Pivotal and Dan Baskette, Pivotal
Previous
Delaying Asynchronous Message Processing

Next
Eventual Consistency: Decoupling Microservices with Spring AMQP and RabbitMQ
Eventual Consistency: Decoupling Microservices with Spring AMQP and RabbitMQ