RabbitMQ Messaging — Spring Boot 3.4 Architecture Blueprint

Scaffold production-ready RabbitMQ Messaging for Spring Boot 3.4: Enterprise AMQP message broker with direct/topic/fanout exchanges and dead-letter queue error handling. Pre-wired JPA, starters, and Docker Compose.

Overview & Architecture Pattern

Enterprise AMQP message broker with direct/topic/fanout exchanges and dead-letter queue error handling.

Architecture Pattern: Messaging & Events

Primary Use Case: Transactional messaging, guaranteed at-least-once delivery, and background worker queues.

Included Dependencies & Starters

spring-boot-starter-web, spring-boot-starter-amqp, validation

Domain Entities & Scaffolding Defaults

QueueMessage (exchange, routingKey, payload, status, retryCount)

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 RabbitMQ Messaging blueprint?
The RabbitMQ Messaging blueprint includes spring-boot-starter-web, spring-boot-starter-amqp, validation, pre-configured application.yml properties, and production-ready connection pools.
How do I run the generated RabbitMQ 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.