实时数据推送架构
设计用于向已连接客户端持续推送数据流和更新的架构。
实时数据推送架构 是 CoddyKit 上的免费 WebSockets & Real-Time Systems with Spring 课时。 这是第 2 节课，共 4 节。 你可以在下方免费阅读本课时的完整内容 — 然后在浏览器中使用内置代码编辑器和全天候 AI 导师进行实践。 这是 WebSockets & Real-Time Systems with Spring 学习路径的一部分，你的进度在网页和 CoddyKit 应用中同步。 WebSockets & Real-Time Systems with Spring 课程共包含 4 节课。
本课时的部分内容尚未翻译，以英文显示。
Real-Time Data Push
Modern applications thrive on instant updates. Imagine a stock ticker, a sports score app, or a chat room – all need data delivered as it happens, not on request.
This lesson explores how to design server-side architectures that actively push continuous data streams and updates to connected clients.
Publisher-Subscriber Model
At the core of data push is the Publisher-Subscriber (Pub/Sub) pattern. Here's how it works:
- Publishers: These are server-side components that generate and send messages.
- Subscribers: These are connected clients (e.g., web browsers, mobile apps) that express interest in specific types of messages.
The system delivers messages from publishers to all interested subscribers, decoupling the data source from its consumers.
Server-Side Data Sources
Where does the data you want to push originate? Common sources include:
- Database Changes: Real-time updates when data in your database is modified.
- External APIs: Events or data received from third-party services.
- Internal Application Events: Actions within your own application (e.g., a new order placed, a user status change).
- Message Queues: Data consumed from systems like Kafka or RabbitMQ.
Your push architecture acts as a bridge, taking data from these sources and sending it to clients.
Spring Push Service Example
Let's see a simple Spring Boot service that simulates generating and pushing data to a STOMP topic. We use SimpMessagingTemplate, Spring's helper for sending messages to broker destinations.
Try running this example:
import org.springframework.boot.SpringApplication;
import org.springframework.boot.autoconfigure.SpringBootApplication;
import org.springframework.context.annotation.Configuration;
import org.springframework.messaging.simp.SimpMessagingTemplate;
import org.springframework.messaging.simp.config.MessageBrokerRegistry;
import org.springframework.scheduling.annotation.EnableScheduling;
import org.springframework.scheduling.annotation.Scheduled;
import org.springframework.stereotype.Service;
import org.springframework.web.socket.config.annotation.EnableWebSocketMessageBroker;
import org.springframework.web.socket.config.annotation.StompEndpointRegistry;
import org.springframework.web.socket.config.annotation.WebSocketMessageBrokerConfigurer;
import java.time.LocalDateTime;
import java.time.format.DateTimeFormatter;
// Main Spring Boot Application
@SpringBootApplication
@EnableScheduling // Enables scheduled tasks like our data push
@EnableWebSocketMessageBroker // Enables STOMP over WebSockets
public class RealTimeApp {
public static void main(String[] args) {
SpringApplication.run(RealTimeApp.class, args);
}
}
// WebSocket Configuration for STOMP
@Configuration
@EnableWebSocketMessageBroker
class WebSocketConfig implements WebSocketMessageBrokerConfigurer {
@Override
public void configureMessageBroker(MessageBrokerRegistry config) {
// Enable a simple in-memory broker for '/topic' and '/user' destinations
config.enableSimpleBroker("/topic", "/user");
// Prefix for messages from clients to server-side @MessageMapping methods
config.setApplicationDestinationPrefixes("/app");
}
@Override
public void registerStompEndpoints(StompEndpointRegistry registry) {
// Register the '/ws' endpoint for WebSocket handshake
registry.addEndpoint("/ws").withSockJS();
}
}
// Service to push real-time data
@Service
class DataPushService {
private final SimpMessagingTemplate messagingTemplate;
private int counter = 0;
public DataPushService(SimpMessagingTemplate messagingTemplate) {
this.messagingTemplate = messagingTemplate;
}
// This method runs every 3 seconds and pushes data
@Scheduled(fixedRate = 3000)
public void pushTimeUpdate() {
String message = "Current time: " + LocalDateTime.now().format(DateTimeFormatter.ofPattern("HH:mm:ss")) + " (Update " + (++counter) + ")";
// Push to a public topic. Clients can subscribe to '/topic/updates'.
messagingTemplate.convertAndSend("/topic/updates", message);
System.out.println("Pushed to /topic/updates: " + message);
}
}Broadcasting Updates
The example in the previous scene demonstrates broadcasting. When our DataPushService sends a message to /topic/updates, it's pushed to all clients currently subscribed to that topic.
- This is ideal for public data streams like chat rooms, news feeds, or global notifications.
- It's an efficient fan-out architecture, where a single message from the server reaches multiple clients simultaneously.
Targeted Push: Topics & Users
While topics are great for broadcasting, sometimes you need to send messages to a specific user or a small group. STOMP supports two main types of destinations for pushing data:
- Topics (e.g.,
/topic/news): For broadcasting messages to all subscribers. - User Destinations (e.g.,
/user/{userId}/queue/notifications): For sending private, user-specific messages.
Understanding this distinction is crucial for designing flexible push architectures.
Private User Notifications
To send a private message or notification to a specific user, Spring's SimpMessagingTemplate provides the convertAndSendToUser() method.
This method automatically routes the message to the correct WebSocket session(s) associated with that user ID.
import org.springframework.messaging.simp.SimpMessagingTemplate;
import org.springframework.stereotype.Service;
@Service
public class NotificationService {
private final SimpMessagingTemplate messagingTemplate;
public NotificationService(SimpMessagingTemplate messagingTemplate) {
this.messagingTemplate = messagingTemplate;
}
public void sendPrivateNotification(String userId, String message) {
// The client would subscribe to '/user/queue/notifications'
// Spring handles the '/user/{userId}' part automatically.
messagingTemplate.convertAndSendToUser(userId, "/queue/notifications", message);
System.out.println("Sent private notification to " + userId + ": " + message);
}
}External Event Integration
For complex, high-volume, or distributed systems, your data sources might be external message brokers like Apache Kafka or RabbitMQ.
Your push architecture would involve:
- A Spring component acting as a consumer, listening to messages from the external broker.
- Upon receiving a message, this component then uses
SimpMessagingTemplateto push the data via WebSockets to relevant clients.
This pattern ensures loose coupling and scalability.
Scaling Push Architectures
As your application grows, you'll need to scale your data push system:
- Horizontal Scaling: Run multiple instances of your WebSocket server.
- External Message Brokers: Essential for inter-server communication when horizontally scaled. They ensure messages reach all relevant clients, regardless of which server instance they're connected to.
- Load Balancers: Distribute client connections across your server instances. Sticky sessions might be needed for simple setups, or more advanced session management for complex ones.
Architecture Quiz
You're building a real-time application. Users need to receive updates about their own specific orders, while also seeing a public feed of recently placed orders by everyone. Which architectural approach is best for each scenario?
Recap: Data Push Mastery
You've now explored the essential concepts behind real-time data push architectures:
- The Publisher-Subscriber model as a foundation.
- Identifying various server-side data sources.
- Implementing broadcasting via topics and private notifications via user destinations in Spring.
- Understanding the role of external event sources and strategies for scaling your push system.
This knowledge empowers you to design robust and efficient real-time data delivery for any application!
常见问题解答
「实时数据推送架构」课时是免费的吗？
是的 — 「实时数据推送架构」的完整文本可在网页上免费阅读。要进行交互式练习（内置代码编辑器和全天候 AI 导师）并解锁 WebSockets & Real-Time Systems with Spring 课程的其余内容，请升级到 CoddyKit PRO。 WebSockets & Real-Time Systems with Spring 课程共包含 4 节课。
「实时数据推送架构」这节课中我会学到什么？
设计用于向已连接客户端持续推送数据流和更新的架构。 你通过在浏览器中直接运行的动手代码来练习 WebSockets & Real-Time Systems with Spring，全天候 AI 导师会在你学习这节课的过程中回答你的问题。
学习 WebSockets & Real-Time Systems with Spring 需要有经验吗？
无需任何先前经验。CoddyKit 上的 WebSockets & Real-Time Systems with Spring 课程适合初学者到高级学习者，你可以从这里开始或从头开始，按照自己的节奏学习。 这是第 2 节课，共 4 节。
「实时数据推送架构」课时需要多长时间？
大多数 CoddyKit 课程大约需要 5–10 分钟。每节课都很精短且互动，所以你能稳步进步，并在网页和应用中从离开的地方继续。
我能在这节 WebSockets & Real-Time Systems with Spring 课中编写并运行代码吗？
能。每节 WebSockets & Real-Time Systems with Spring 课都包含内置代码编辑器，你可以在浏览器中直接编写并运行真实代码，并获得即时 AI 反馈 — 无需本地设置。