WebSockets & Real-Time Systems with Spring · درس

بنيات دفع البيانات الفورية

صمّموا بنيات لدفع تدفقات البيانات والتحديثات المستمرة إلى العملاء المتصلين.

بنيات دفع البيانات الفورية درس مجاني في WebSockets & Real-Time Systems with Spring على CoddyKit. هذا هو الدرس 2 من أصل 4. يمكنك قراءة الدرس كاملاً أدناه مجاناً — ثم تمرن عليه مباشرة في المتصفح باستخدام محرر أكواد مدمج ومدرس ذكاء اصطناعي متاح 24/7. هذا الدرس جزء من مسار التعلم في 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 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!

الأسئلة الشائعة

هل درس «بنيات دفع البيانات الفورية» مجاني؟

نعم — نص درس «بنيات دفع البيانات الفورية» كامل متاح مجاناً هنا على الويب. لتمرينه بشكل تفاعلي (محرر أكواد مدمج ومدرس ذكاء اصطناعي متاح 24/7) وفتح باقي دورة WebSockets & Real-Time Systems with Spring، انتقل إلى CoddyKit PRO. تتضمن دورة WebSockets & Real-Time Systems with Spring 4 دروس في المجموع.

ماذا ستتعلم في «بنيات دفع البيانات الفورية»؟

صمّموا بنيات لدفع تدفقات البيانات والتحديثات المستمرة إلى العملاء المتصلين. تتمرن على WebSockets & Real-Time Systems with Spring مع أكواد عملية تشغلها مباشرة في المتصفح، ومدرس ذكاء اصطناعي متاح 24/7 يجيب على أسئلتك أثناء عملك.

هل أحتاج إلى خبرة سابقة لأبدأ WebSockets & Real-Time Systems with Spring؟

لا تُشترط خبرة سابقة. WebSockets & Real-Time Systems with Spring على CoddyKit منظم للمبتدئين حتى المتقدمين، لذا يمكنك البدء من هنا أو من البداية والتقدم بسرعتك الخاصة. هذا هو الدرس 2 من أصل 4.

كم من الوقت يستغرق درس «بنيات دفع البيانات الفورية»؟

معظم دروس CoddyKit تستغرق حوالي 5–10 دقائق. كل منها موجز وتفاعلي، لذا تحرز تقدماً مستمراً وتستأنف من حيث توقفت عبر الويب والتطبيق.

هل يمكنني كتابة وتشغيل أكواد في درس WebSockets & Real-Time Systems with Spring هذا؟

نعم. كل درس في WebSockets & Real-Time Systems with Spring يتضمن محرر أكواد مدمج، لذا تكتب وتشغل أكواداً حقيقية مباشرة في متصفحك وتحصل على تعليقات فورية من الذكاء الاصطناعي — بدون إعداد محلي.

جميع الدروس في هذه الدورة

الأحداث المرسلة من الخادم (SSE) مقابل WebSockets
بنيات دفع البيانات الفورية
تنفيذ إشعارات المستخدمين
تتبع الحضور وحالة الاتصال

← العودة إلى WebSockets & Real-Time Systems with Spring