01Legacy / integration
Rewriting SOAP/Apache Camel integrations in Spring Boot 3
Better compatibility with newer services, and new developers no longer lose time learning old Camel route logic.
- Java
- Spring Boot 3
- Apache Camel
- SOAP
Case studies
Problems I worked on, what I did, and what came out of it. Each one is from a job or project listed on my CV.
Better compatibility with newer services, and new developers no longer lose time learning old Camel route logic.
CPU spike gone at peak sportsbook traffic, for a few MB of added memory.
About 2,300 lines of copied parser code replaced by one shared scraper; most banks are now around fifteen lines of configuration.
Clients talk to one gateway, and authentication lives in one place.
Releases became visible and reliable again across 5 services.