Необходимость внешних брокеров сообщений

Welcome! Modern web applications often need to communicate in real-time. Think about chat apps, live dashboards, or online games.

As your app grows, more users will connect simultaneously. This lesson explores a key challenge: how do you keep your real-time system fast and reliable when handling thousands or millions of users?

When you first set up a Spring WebSocket application, you typically use an in-memory message broker (like Spring's SimpleBrokerMessageHandler).

An in-memory broker lives directly within your application's process. It handles message routing and subscriptions for all clients connected to that specific application instance.

On a single server, an in-memory broker works perfectly. All WebSocket clients connect to the same application instance, and therefore, to the same in-memory broker.

• Client A sends a message.
• The in-memory broker receives it.
• The broker routes it to Client B and Client C, which are also connected to this same server.

Everything runs smoothly in a single-instance setup!

To handle more users than a single server can manage, applications are often deployed in a cluster. This means running multiple instances of your application.

A load balancer sits in front of these instances, distributing incoming client connections across them. For example, Client A might connect to Server 1, and Client B to Server 2.

Here's where the problem arises: with multiple server instances, each instance has its own, separate in-memory broker.

These brokers are completely isolated. They don't know about each other, and they don't share any information.

Imagine this scenario:

• Client A connects to Server 1.
• Client B connects to Server 2.
• Client A sends a message to a public chat topic.

Only the in-memory broker on Server 1 receives this message. It will correctly deliver it to any other clients connected to Server 1, but Client B on Server 2 will never receive it!

For a truly scalable real-time application, messages must be delivered to all relevant clients, regardless of which server instance they are connected to.

The in-memory broker prevents this by creating isolated 'silos' of messages. We need a way for all server instances to communicate and share messages.

This is where external message brokers come in. These are standalone services (like RabbitMQ, Apache Kafka, or Redis Pub/Sub) that operate independently of your application instances.

Instead of each server having its own broker, all your server instances connect to a single, centralized external broker.

With an external broker:

• A client sends a message to its connected server instance.
• That server instance immediately forwards the message to the external broker.
• The external broker then distributes the message to all other connected server instances.
• Each server instance then delivers the message to its own connected clients.

This ensures all clients receive messages, regardless of which server they are connected to.

Using an external message broker offers significant benefits for scalable real-time applications:

• Horizontal Scalability: Easily add or remove server instances without affecting message delivery.
• Reliability: Many external brokers offer message persistence, ensuring messages aren't lost even if a server instance goes down.
• Decoupling: Your WebSocket server instances become stateless, making them easier to manage and scale independently.

In this lesson, we explored the crucial need for external message brokers when scaling Spring WebSocket applications.

• In-memory brokers work well for single instances but fail in distributed environments.
• Load balancers distribute connections, but in-memory brokers create message silos.
• External brokers (like RabbitMQ, Kafka) provide a centralized hub for message exchange, enabling true horizontal scalability and reliability for your real-time systems.

Next, we'll dive into integrating these external solutions!