Modernizing a multi-tenant platform without pausing active deploys.
- Context
- A memory-intensive monolith, blocking workloads, and per-client file configuration no longer matched the product's multi-tenant direction.
- What I owned
- Hands-on ownership of backend architecture, infrastructure, deploys, production, and the modernization path.
- Key decisions
- Kubernetes-based workload separation, database-driven tenant configuration, RabbitMQ-backed asynchronous processing, and incremental replacement.
- Current result
- Long-running work moved out of request paths. Tenant onboarding moved from manual file changes across deployments to a database-driven workflow. Workloads gained clearer scaling boundaries while active deploys continued.