Customer Master Data — Strangler Migration
Modernized a mission-critical Customer Master Data monolith into Java/Spring microservices via the strangler pattern, while migrating from OpenShift to AWS EKS. Zero ticket from legacy consumers.
Three-and-a-half years inheriting a mission-critical CMD monolith and a plan: move to microservices without stopping global operations. Strangler pattern with adapter layer in front of the legacy API speaking the old contract verbatim, feature-by-feature routing (not endpoint-by-endpoint), parallel-write window during data migration with divergence metrics. PL/SQL migration AND rollback scripts from day one.
Result: monolith shrunk, team got an evolvable platform, legacy consumers never filed a ticket.
Stack
Java, Spring Boot, Kafka, PostgreSQL, Oracle, Elasticsearch, AWS EKS, OpenShift, Pulumi