Skip to content

Migrate to distributed microservices architecture with API gateway - #18

Open
sohail24 wants to merge 4 commits into
mainfrom
prod-v2.004
Open

Migrate to distributed microservices architecture with API gateway#18
sohail24 wants to merge 4 commits into
mainfrom
prod-v2.004

Conversation

@sohail24

@sohail24 sohail24 commented Sep 2, 2026

Copy link
Copy Markdown
Owner

No description provided.

…dis and RabbitMQ for distributed rate limiting and event notifications.
… and update docker-compose to route traffic through the new gateway service.
…eway and extracted bell service

- Add Spring Cloud Gateway (api-gateway:8080) for reactive routing, edge JWT validation, and centralized CORS management.
- Implement edge JWT blacklist filter using Reactive Redis (ReactiveStringRedisTemplate) for instant logout revocation.
- Extract Bell domain from monolith into standalone microservice (bell-service:8085) with Redis TTL rate-limiting and RabbitMQ integration.
- Decouple OrderService and BellService using RabbitMQ Topic Exchange (quickmenu.events) and DLQ topology.
- Add notification-service:8084 as standalone AMQP consumer pushing real-time STOMP WebSocket frames to staff dashboard.
- Enforce single-responsibility CORS pattern at Gateway edge and add CorsHeaderSuppressorFilter to eliminate duplicate Access-Control-Allow-Origin headers.
- Configure dynamic server.port (${SERVER_PORT}) and Java 17 target bytecode compatibility across all microservices.
@vercel

vercel Bot commented Sep 2, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
quick-menu Ready Ready Preview Sep 2, 2026 9:31pm UTC

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant