Project Overview
A full shopping platform built as a distributed system instead of a monolith — services for Auth, Products, Orders, and Notifications talk through a message broker so checkout, warehouse, and email flows stay async and independently scalable. The storefront is Next.js (App Router) with SSR/ISR for SEO, backed by ASP.NET Core Web APIs, PostgreSQL, and Redis caching, with RabbitMQ or Apache Kafka for event-driven and CQRS-style communication.
Challenge
A monolith can run a catalog, but high-traffic checkout, warehouse alerts, and email cannot scale or fail independently. The work was to prove a distributed, event-driven shop instead of another single-app market.
Solution
I split the backend into ASP.NET Core services (Auth, Products, Orders, Notifications) linked by RabbitMQ or Kafka so order completion fans out async to stock and email. Next.js App Router uses SSR/ISR for SEO; PostgreSQL holds source data and Redis caches hot reads, with CQRS-style command/query paths where load needs it.
Result
The architecture shows companies a shop that absorbs load by scaling services, not the whole stack — a clear signal of scalable and event-driven design.
Technologies used
Features
Need a similar system — or a new one?
Tell me about your idea, stack, timeline, or an existing product you want improved.
