Design Microservices Architecture with Patterns and Principles - Challenges of Asynchronous Communication

The video discusses challenges in asynchronous communication, focusing on single points of failure in message brokers, debugging difficulties, and issues with message delivery and order. It suggests using hybrid communication, generating unique IDs for tracking, and embracing message delivery mechanisms with item potency.

What is a major risk associated with message brokers in asynchronous communication?

• They require too much bandwidth.

• They are too expensive to maintain.

• They can become a single point of failure.

• They are too fast for synchronous systems.

What strategy is suggested to avoid relying on a single node in message brokers?

• Increasing the message size.

• Reducing the number of nodes.

• Scaling and using hybrid communication.

• Using only synchronous communication.

Why is debugging asynchronous communication often challenging?

• It requires specialized hardware.

• Messages are always encrypted.

• There is no clear data flow across service boundaries.

• It is too costly.

What is a correlation ID used for in asynchronous communication?

• To encrypt messages.

• To track messages across systems.

• To compress data.

• To prioritize messages.

What is a common characteristic of message broker systems regarding message delivery?

• They require manual message sorting.

• They always deliver messages in real-time.

• They use at least once delivery.

• They guarantee message order.