Overview / Context
The existing logistics platform contained functionality inside a monolithic application. Modernization work focused on separating appropriate functionality into Spring Boot services while keeping existing workflows working in production.
Problem
The challenge was to move appropriate functionality out of a monolith without breaking workflows that already depended on production behavior.
This was not just moving code between repositories. It required understanding existing behavior and making sure extracted functionality still supported existing use cases.
This application was also running on a really old version of Spring Boot and Java, so modernization work also involved upgrading the application to a newer version of Spring Boot and Java while preserving existing workflows.
Approach / Implementation
- Participated in modernization work that moved monolith functionality into Spring Boot services.
- Worked with API Gateway routing as functionality was separated into services.
- Worked with Eureka service discovery for service-to-service resolution.
- Worked with OAuth2-protected resource services.
- Worked with Kubernetes-based service deployment.
Important Engineering Details
A major part of the work was understanding existing system behavior before extraction so workflows would continue to function after separation.
The implementation combined service extraction, routing, discovery, security, and deployment concerns rather than a single isolated code change.
My Contribution
I was hands-on with implementation and also worked through architectural decisions around how functionality should be separated and how modernization changes should fit into existing production systems.
This work included architectural ownership within the modernization effort, while still being closely tied to implementation.
Result
The extracted services could be deployed more independently while preserving existing workflows.