Application Modernization with Camel JavaScript and OpenShift
summary
Apache Camel runs JavaScript via JSR‑223 and Camel K runs integrations natively on OpenShift, using S2I images and the Camel K CLI to push single-file routes; the first build pulls and builds an image in ~2 minutes and subsequent updates take a few seconds, with redeploy almost instantaneous. Camel provides ~300 components for JMS, REST and transformations, supports REST DSL and saga compensation patterns, and uses ConfigMaps and operators for automated deployments.
AI-written summary · about
chapters (31)
- 0:00Introduction
- 0:23Application Modernization
- 1:15Dependencies
- 2:09Apache Camel
- 2:54Integration Patterns
- 4:42Apache Camo
- 5:10Camel Routes
- 6:04Example Inbox
- 6:32REST DSL
- 7:13Camel JavaScript
- 9:19Properties
- 9:55External Resources
- 10:14Panel Dependencies
- 11:51Apache Camel K Configuration
- 12:18Camel K Performance
- 12:53How does KML work
- 13:35Camel Run with KML
- 15:15Deploy JavaScript on OpenShift
- 16:08HighLevel Architecture
- 17:02Surface Architecture
- 20:40KNative Building Blocks
- 21:55KNative Serving
- 22:28Reduce Operational Cost
- 22:45Traditional IT Organization
- 24:03Service granularity
- 25:00Saga pattern
- 27:25Source to image deployment
- 27:46Configuration injection
- 28:27Openshift surface
- 28:38Install operator
- 28:51Conclusion
related talks
39m~1 sec. Java app redeployments on Kubernetes
35mGetting further with Apache Camel on Quarkus
42mIntegration in the cloud era with Camel Quarkus
37mBuilding Cloud Integration Applications Through Knative and...
45mOpenShift the power of Kubernetes for developers
20mApplication Modernization: From Concept to Kubernetes
43mFrom Camel to Kamelets: new connectors for event-driven applications
01h 06mOpenShift - the power of Kubernetes for engineers