Mallify
Event-driven e-commerce marketplace on a microservices architecture

About
Context, problem & solution
Mallify is a full-stack e-commerce marketplace built to explore microservices at real scale — decomposed into more than eighteen independent services communicating through events.
Context and goal. A marketplace touches many concerns at once: user accounts, product catalogs, carts, orders, payments, notifications. Bundling all of that into one application makes it fragile and hard to scale. Mallify takes the opposite approach: split the domain into small, independently deployable services so each can evolve, scale, and fail in isolation without taking the whole platform down.
Solution. The system is organized as 18+ microservices, each owning a slice of the domain and its own data in MongoDB. Services communicate in an event-driven style rather than through tight synchronous coupling, which keeps them decoupled and lets the platform absorb load by scaling only the services that need it. Everything is containerized with Docker so each service runs, ships, and scales as an independent unit. The design supports multiple roles (buyers, sellers/administration), reflecting the real shape of a marketplace.
Engineering focus. The value of this project is architectural: it demonstrates service decomposition, per-service data ownership, and event-driven communication — the foundations of a scalable distributed system. (This case study is written from the repository description; the project has no README yet. Adding a README on GitHub with the exact service list, broker, and run instructions would let this page be even more precise — happy to help draft one.)
Architecture
How the system is built
Tech stack
Technologies used
Architecture
Backend
Database
DevOps
Want to know more about Mallify?
The complete source code is available on GitHub, along with the history and deployment configuration.