Need for External Message Brokers
Understand the limitations of in-memory brokers for scaling and the advantages of external solutions.
Scaling Real-Time Apps
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?
Understanding In-Memory Brokers
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.
All lessons in this course
- Need for External Message Brokers
- Integrating with RabbitMQ/Kafka
- Distributed WebSocket Architectures
- Configuring the STOMP Broker Relay