WebSocket & STOMP Messaging — Spring Boot 3.4 Architecture Blueprint

Scaffold production-ready WebSocket & STOMP Messaging for Spring Boot 3.4: Bidirectional STOMP broker, SockJS fallback, /topic and /queue brokers, and JWT channel security interceptors. Pre-wired JPA, starters, and Docker Compose.

Overview & Architecture Pattern

Bidirectional STOMP broker, SockJS fallback, /topic and /queue brokers, and JWT channel security interceptors.

Architecture Pattern: Real-Time & Messaging

Primary Use Case: Live status dashboards, financial market price feeds, collaborative real-time editors.

Included Dependencies & Starters

spring-boot-starter-web, spring-boot-starter-websocket, spring-boot-starter-security

Domain Entities & Scaffolding Defaults

WebSocketPayload (destination, sender, payload, timestamp)

Quickstart: Running Your Project

# 1. Start required infrastructure containers
docker compose up -d

# 2. Run the Spring Boot 3.4 application (Maven)
./mvnw spring-boot:run

# Or run with Gradle
./gradlew bootRun

Frequently Asked Questions

What starters are included in the WebSocket & STOMP Messaging blueprint?
The WebSocket & STOMP Messaging blueprint includes spring-boot-starter-web, spring-boot-starter-websocket, spring-boot-starter-security, pre-configured application.yml properties, and production-ready connection pools.
How do I run the generated WebSocket & STOMP Messaging project locally?
Extract the downloaded ZIP, start dependencies with 'docker compose up -d', and execute './mvnw spring-boot:run' (Maven) or './gradlew bootRun' (Gradle).
Can I customize entities and database schemas in this blueprint?
Yes, SpringForge allows you to visually add or modify JPA entities, field types, validation rules, and relational mappings, or import SQL DDL schemas.