การผสาน WebSockets เข้ากับ Spring

Welcome! In this lesson, we'll integrate WebSockets with Spring Boot. This is crucial for enabling real-time features like GraphQL Subscriptions.

WebSockets provide a persistent, two-way communication channel between a client and a server over a single, long-lived TCP connection.

Unlike traditional HTTP requests (which are short-lived), GraphQL Subscriptions require a continuous connection to push data updates to clients as they happen.

WebSockets are the perfect fit because they maintain an open connection, allowing the server to send data to the client at any time without a new request.

First, we need to add the Spring Boot WebSocket starter dependency to our project. This brings in all the necessary libraries to enable WebSocket support.

For Gradle, add this to your build.gradle:

In Spring, we use annotations to enable specific functionalities. For WebSockets with a message broker, we use @EnableWebSocketMessageBroker.

This annotation enables a STOMP over WebSocket message broker, which is a powerful way to handle messaging.

We need a configuration class that extends WebSocketMessageBrokerConfigurer. This class allows us to customize our WebSocket setup.

The registerStompEndpoints() method is used to define the URL endpoint clients will connect to for WebSocket communication.

When registering an endpoint, we often add .withSockJS(). SockJS is a JavaScript library that provides a WebSocket-like API.

It offers fallback options (like HTTP streaming or long polling) for browsers that don't fully support WebSockets or in environments with proxies that interfere.

The configureMessageBroker() method sets up the message broker itself. This defines how messages are routed between clients and the application.

• enableSimpleBroker("/topic"): Enables an in-memory message broker for destinations prefixed with /topic. Clients subscribe to these topics.
• setApplicationDestinationPrefixes("/app"): Defines prefixes for messages destined for methods annotated with @MessageMapping in our application.

Here's a minimal Spring Boot application demonstrating the WebSocket configuration. Try running it to see Spring initialize the WebSocket server!

With this WebSocket infrastructure, our GraphQL subscription resolvers (from the previous lesson) can now publish events.

When a resolver publishes an event, Spring's message broker ensures that all clients subscribed to the relevant /topic are immediately notified via their open WebSocket connection.

Great job! You've learned how to integrate WebSockets with Spring Boot to provide a robust real-time communication layer.

• We added the WebSocket starter dependency.
• We used @EnableWebSocketMessageBroker and WebSocketMessageBrokerConfigurer.
• We configured STOMP endpoints (e.g., /ws-connect with SockJS).
• We set up a message broker with prefixes like /topic for subscriptions and /app for app-specific messages.

This setup is the foundation for delivering real-time GraphQL Subscriptions!