creation / released
ManageRestaurantApp
Restaurant system with 3 user roles, 3 payment strategies, WebSocket kitchen updates, and retryable RabbitMQ events.
about this build
The mission
I contributed to user and dish workflows across the Spring backend and React screens, including chef-facing UI. The application covers customer, chef and admin flows for reservations, orders and payments; payment behavior is separated into Cash, MoMo and ZaloPay strategies.
Code-level metrics: 3 roles, 3 payment strategies, 3 RabbitMQ business queues (email, chef notification and analytics) plus 1 dead-letter queue. The consumer configuration allows up to 3 processing attempts before failed messages are rejected. WebSocket configuration supports live order/kitchen updates. These figures describe implemented paths, not transaction volume or payment success rate.
Role: Contributed Spring user/dish workflows and React chef screens in a team project; participated in asynchronous event handling.
technology
Primary GitHub language: Java
system highlights
- 3 roles and 3 payment strategies
- WebSocket order/kitchen updates
- 3 RabbitMQ queues + 1 DLQ; up to 3 attempts
HOW IT WAS BUILT
Skills & technology in this project
Skills applied
- Role-based business workflows
- Payment Strategy pattern
- Real-time order updates
- Message retries and dead-letter handling
Languages
- Java
- JavaScript
- HTML
- CSS
Tools & platforms
- Spring
- React
- WebSocket
- RabbitMQ
- MoMo
- ZaloPay