Architecture decision · e-commerce
Monolith to microservices migration for an e-commerce platform
Backend / Platform PythonFastAPIPostgreSQLRedisDockerTraefik
┌──► auth monolith ───┼──► catalog / CMS FastAPI · PostgreSQL · Redis (legacy) └──► ugc: chats, reviews behind Traefik + CDN
Problem
A growing e-commerce platform was built as a monolith; deployments were risky, scaling was all-or-nothing, and the system was hard to extend for international expansion.
Approach
Migrated incrementally with an expand/contract (strangler-fig) approach — extract a service, run it alongside the monolith, prove it in production, then cut over while keeping rollback live. Configured infrastructure with Traefik, Cloudflare, and CDN.
Result
A scalable, fault-tolerant, easily extensible system ready for international expansion — migrated live at ~100% uptime, with the business never pausing delivery.
Evidence
Described in work history (Amit agency, 2020–2022); the platform (hodoor.com) shipped on this architecture.
Available for: public discussion
The migration was incremental by design: each extracted service had to prove itself in production before the next cut, with rollback kept live — so the business never stopped shipping.