Monolith is slowing down need safe migration path. Architecture, tools, rollback strategies?
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Hey, use the Strangler Fig pattern build new services behind a facade, cut over traffic gradually. Start with a non-critical domain, such as “user profile.” Tools: Kong API gateway, Kubernetes namespaces, Jaeger tracing. Rollback: Blue-green deploys. Migrate one service/month. My team provided six services with zero downtime.
Pick a bounded context first (one business capability). Event-driven with Kafka decouples services. Contract testing prevents breakages. Observability stack: Prometheus metrics + Grafana dashboards. Start small: Extract the auth service. Pro tip: Keep the shared DB read-only during transition. Went from 1 → 12 services smoothly.