WebSockets & Real-Time Systems with Spring · Aula

Arquiteturas de envio de dados em tempo real

Conceba arquiteturas para enviar fluxos contínuos de dados e atualizações aos clientes ligados.

Arquiteturas de envio de dados em tempo real é uma aula grátis de WebSockets & Real-Time Systems with Spring no CoddyKit. Esta é a aula 2 de 4. Você pode ler a aula completa abaixo gratuitamente — depois pratica ao vivo no navegador com um editor de código integrado e um tutor de IA 24/7. Faz parte do caminho de aprendizado de WebSockets & Real-Time Systems with Spring, e seu progresso é sincronizado entre a web e o app CoddyKit. O curso de WebSockets & Real-Time Systems with Spring inclui 4 aulas no total.

Partes desta aula ainda não foram traduzidas e aparecem em inglês.

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 SimpMessagingTemplate to 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!

Perguntas Frequentes

A aula “Arquiteturas de envio de dados em tempo real” é grátis?

Sim — o texto completo de “Arquiteturas de envio de dados em tempo real” é grátis para ler aqui na web. Para praticá-la interativamente (um editor de código integrado e um tutor de IA 24/7) e desbloquear o restante do curso de WebSockets & Real-Time Systems with Spring, atualize para CoddyKit PRO. O curso de WebSockets & Real-Time Systems with Spring inclui 4 aulas no total.

O que vou aprender em “Arquiteturas de envio de dados em tempo real”?

Conceba arquiteturas para enviar fluxos contínuos de dados e atualizações aos clientes ligados. Você pratica WebSockets & Real-Time Systems with Spring com código prático que executa diretamente no navegador, e um tutor de IA 24/7 responde suas dúvidas enquanto trabalha na aula.

Preciso ter experiência prévia para começar WebSockets & Real-Time Systems with Spring?

Nenhuma experiência prévia é necessária. WebSockets & Real-Time Systems with Spring no CoddyKit é estruturado para alunos iniciantes até avançados, então você pode começar aqui ou desde o início e aprender no seu ritmo. Esta é a aula 2 de 4.

Quanto tempo leva a aula “Arquiteturas de envio de dados em tempo real”?

A maioria das aulas CoddyKit leva cerca de 5–10 minutos. Cada uma é compacta e interativa, então você faz progresso constante e retoma exatamente de onde parou entre web e app.

Posso escrever e executar código nesta aula de WebSockets & Real-Time Systems with Spring?

Sim. Cada aula de WebSockets & Real-Time Systems with Spring inclui um editor de código integrado, então você escreve e executa código real direto no navegador e recebe feedback de IA instantaneamente — nenhuma configuração local necessária.

Todas as aulas deste curso

Eventos enviados pelo servidor (SSE) vs. WebSockets
Arquiteturas de envio de dados em tempo real
Implementação de notificações de utilizador
Acompanhamento da presença e do status online

← Voltar para WebSockets & Real-Time Systems with Spring