Rewriting SOAP/Apache Camel integrations in Spring Boot 3
Legacy integration services with 20+ endpoints each, moved to Spring Boot 3 without losing the business logic inside them.
- Role
- Software developer at Intellexi, led the rewrite
- Outcome
- Better compatibility with newer services, and new developers no longer lose time learning old Camel route logic.
- Stack
- Java
- Spring Boot 3
- Apache Camel
- SOAP
- Docker
- OpenShift
Problem
Integration services built on SOAP and Apache Camel, each exposing 20+ endpoints, had become hard to work with. They did not fit well with the newer services around them, and every new developer spent time learning the old Camel route logic before they could change anything.
Approach
I led the rewrite of these services into Spring Boot 3, keeping the existing business behaviour intact.
Result
- Compatibility with newer services improved.
- New-developer ramp-up no longer included learning Camel routes.