Evolution of messaging systems and event-driven architecture

Suresh Pandey explores event-driven architecture and explains why modern messaging brokers are game changers for distributed applications. You'll learn what it takes to build a distributed application using eventing (and the benefits of doing so) and dive into offerings from RabbitMQ, Kafka, and Kinesis so you can determine which is suitable for your application.

Messaging is a core component in distributed applications and allows asynchronous communication between microservices. An event-driven architecture has several advantages over point-to-point communication and promotes loose coupling of services. Messaging brokers minimize the impact on both the source and target systems, reducing the cost of enterprise application integration and maximizing flexibility. Message brokers place a processing layer between the disparate applications and their platforms, accounting for the differences in application semantics, design patterns, data formats, and operating systems within the message broker. However, selecting the right message broker for your needs is a tedious task. There are a number of message brokers available in the market, and each has its own selling point. Since the technology changes so fast, it’s difficult for buyers to explore all available products. In addition, you must take a number factors into consideration when choosing a messaging broke, including a single point of failure, platform support, high availability, scalability, performance, the user interface, and security. Suresh Pandey explores event-driven architecture and explains why modern messaging brokers are game changers for distributed applications. You’ll learn what it takes to build a distributed application using eventing (and the benefits of doing so) and dive into offerings from RabbitMQ, Kafka, and Kinesis so you can determine which is suitable for your application.