Distributed E-Commerce Platform with Microservices and Event-Driven Architecture

A production-style e-commerce platform split into independently deployable microservices communicating over an event bus.

A single large application becomes hard to change as an online shop grows: a bug in payments can bring down the catalog, and every release must be tested and deployed as a whole. Splitting the system into independent services solves this but introduces new problems, such as how services stay consistent without sharing a database. This project builds a distributed e-commerce platform using microservices and event-driven architecture.

The platform is decomposed into catalog, orders, payments and inventory services, each with its own PostgreSQL database and its own release cycle. Services communicate asynchronously through RabbitMQ: when an order is placed, an event triggers payment and inventory reservation, and the saga pattern coordinates the steps and compensates if one fails, for example by releasing stock when a payment is declined. An API gateway gives the React storefront a single entry point and handles authentication and routing. Each service is packaged in Docker and started together with Docker Compose, with health checks and structured logging. The project also covers idempotent message handling so that a repeated message does not charge a customer twice, and tests the system under failure.

You will learn service decomposition, messaging, distributed consistency and containerized deployment. The Project Reference Guide explains the architecture and its trade-offs, and the Reference Implementation includes all services, the gateway, the storefront and set-up steps.