Evolution from ESB to Cloud-native API Integration
summary
Chronicle migrates legacy silos into a cloud-native integration platform that stitches Shopify, Stripe, Salesforce, Marketo, Mailgun and Workcast into an Aurora (MySQL) golden-record store using Apache Camel routes compiled and deployed by Camel K to Kubernetes. The system handles millions of daily events, runs microservices as containerized Spring Boot apps, uses Jenkins and Git-driven CI/CD, Consul for discovery and pub/sub off-ramps, and routinely auto-scales — including scales to zero for low-load routes.
AI-written summary · about
chapters (7)
- 0:00Introduction and context
- 4:48Evolution of integration
- 9:24Integration strategy options
- 13:12Benefits of Camel K
- 21:19Real-world case study
- 27:04Platform architecture
- 33:25Implementation and conclusion
related talks
27mThe journey from legacy to cloud - native success
31mA Journey of Migrating Data Platform from Data Center to Cloud
06mEvolving services from monolithic to modern applications
28mSaaS migration and modernisation
30mMigrating a monolith to Cloud-Native and the stumbling blocks
19mKeynote: From COBOL to Kubernetes: A 250 Year Old Bank's Cloud-Native Journey
28mCloud The Final Destination
01h 01mCloud Integrations, Data Architecture and MDM solutions for Enterprise Applications