4
Services
Auth, product, order, and API gateway.
A Docker Compose microservices environment with auth, product, order, API Gateway, MongoDB, and RabbitMQ event communication.

This project models an e-commerce-style microservices architecture. Services are separated into auth, product, order, and API gateway components, with MongoDB persistence and RabbitMQ message-based communication.
4
Auth, product, order, and API gateway.
2
MongoDB for data and RabbitMQ for message flow.
Docker
Services coordinated through Docker Compose.
Shows understanding of service boundaries, gateway routing, and asynchronous messaging.
Covers auth, product catalog, order handling, REST routing, and shared utilities.
Uses Docker Compose to make a multi-service system runnable as one environment.
This project is repository-first right now. Add a deployed URL to demoUrl, and optionally an iframe-safe URL to demoEmbedUrl, to make it directly interactive here.
Preview not embedded
For static sites, GitHub Pages can be enough. For Next.js and full-stack apps, Vercel, Netlify, Render, Railway, or a Docker host usually gives reviewers a stronger live experience.
Understand how independent backend services communicate without turning every feature into one monolithic API.
Use an API gateway for client entry, service-specific APIs, MongoDB persistence, and RabbitMQ for event-style communication.
A strong backend architecture practice project for discussing service boundaries, message queues, Docker, and Node.js APIs.
Relevant for backend or DevOps-oriented internships.
Good interview topic: why use RabbitMQ, what the gateway does, and how services share configuration.
Shows ability to read and build beyond a single-process app.
A concise view of the product, design, engineering, and delivery decisions behind the final result.
Separated authentication, product, order, and gateway responsibilities.
Connected product/order workflows through RabbitMQ queues.
Used Docker Compose for MongoDB, RabbitMQ, and service startup.