Architetture per il push dei dati in tempo reale
Progetti architetture per inviare flussi continui di dati e aggiornamenti ai client connessi.
Architetture per il push dei dati in tempo reale è una lezione WebSockets & Real-Time Systems with Spring gratuita su CoddyKit. Questa è la lezione 2 di 4. Puoi leggere la lezione completa qui gratuitamente — poi esercitati direttamente nel browser con un editor di codice integrato e un tutor IA disponibile 24/7. Fa parte del percorso di apprendimento WebSockets & Real-Time Systems with Spring, e i tuoi progressi si sincronizzano tra il web e l'app CoddyKit. Il corso WebSockets & Real-Time Systems with Spring include 4 lezioni in totale.
Parti di questa lezione non sono ancora state tradotte e vengono mostrate in inglese.
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!
Impara WebSockets & Real-Time Systems with Spring con un tutor IA — gratis
Scrivi ed esegui vero codice nel tuo browser, ricevi aiuto istantaneo da un tutor IA disponibile 24/7, e riprendi da dove hai lasciato sul web o nell'app.
- Corsi
- 12
- Lezioni
- 48
Domande Frequenti
La lezione «Architetture per il push dei dati in tempo reale» è gratuita?
Sì — il testo completo di «Architetture per il push dei dati in tempo reale» è gratuito qui sul web. Per esercitarvi in modo interattivo (un editor di codice integrato e un tutor IA 24/7) e sbloccare il resto del corso WebSockets & Real-Time Systems with Spring, passa a CoddyKit PRO. Il corso WebSockets & Real-Time Systems with Spring include 4 lezioni in totale.
Cosa imparerò in «Architetture per il push dei dati in tempo reale»?
Progetti architetture per inviare flussi continui di dati e aggiornamenti ai client connessi. Eserciti WebSockets & Real-Time Systems with Spring con codice pratico che esegui direttamente nel browser, e un tutor IA 24/7 risponde alle tue domande mentre lavori sulla lezione.
Ho bisogno di esperienza per iniziare WebSockets & Real-Time Systems with Spring?
Non è richiesta alcuna esperienza precedente. WebSockets & Real-Time Systems with Spring su CoddyKit è strutturato per principianti e studenti avanzati, quindi puoi iniziare da qui o dall'inizio e procedere al tuo ritmo. Questa è la lezione 2 di 4.
Quanto tempo richiede la lezione «Architetture per il push dei dati in tempo reale»?
La maggior parte delle lezioni CoddyKit richiede circa 5–10 minuti. Ogni lezione è breve e interattiva, quindi fai progressi costanti e riprendi esattamente da dove hai lasciato su web e app.
Posso scrivere ed eseguire codice in questa lezione WebSockets & Real-Time Systems with Spring?
Sì. Ogni lezione WebSockets & Real-Time Systems with Spring include un editor di codice integrato, quindi scrivi ed esegui codice reale direttamente nel tuo browser e ricevi feedback istantaneo dall'IA — nessuna configurazione locale necessaria.
Tutte le lezioni di questo corso
- Server-Sent Events (SSE) vs. WebSockets
- Architetture per il push dei dati in tempo reale
- Implementazione delle notifiche utente
- Tracciare la presenza e lo stato online