Enterprise CRM Modernization & Multi-Tenant Platform

Why this work matters

The Product Challenge

The product started with legacy servlet-era Java and needed to evolve without stopping business operations. The target was not a cosmetic refactor; it was a path toward Spring, microservices and tenant-aware architecture.

The challenge was balancing modernization with production continuity: old workflows still had to work while new service boundaries, async jobs and reporting capabilities were introduced.

My Engineering Contribution

• Converted servlet-based modules into Spring-based Java 17 services and later contributed to Java 21 Spring Boot microservices.
• Worked on Kafka-backed async jobs for long-running workflows, reporting and decoupled processing.
• Helped move the CRM architecture toward multi-tenancy so the product could support multiple business customers from a shared platform.
• Built internal HR management capabilities to support operational workflows around the product organization.
• Delivered reporting and workflow modules that made enterprise data easier to process and act on.

System & Product Considerations

• Incremental modernization instead of risky rewrites
• Java 17 to Java 21 migration discipline
• Kafka-backed asynchronous jobs and reporting
• Tenant isolation introduced into an existing enterprise domain
• Internal HR workflows around the CRM ecosystem

Technical Areas

What This Project Taught Me

• Legacy modernization succeeds when each migration step creates business value, not only cleaner code.
• Async jobs and reporting often reveal the real boundaries of an enterprise system.
• Multi-tenancy is hardest when introduced after the product already has years of assumptions.