Camel K and Serverless in Action - When to use it
summary
Camel K runs Camel routes as single-file integrations deployed to Kubernetes or OpenShift via a camel k operator and CLI, using Quarkus for supersonic subatomic Java and optional GraalVM native images. Measured footprints drop from ~218 MB to ~130 MB to ~35 MB and startup from ~9.5s to ~2.5s to sub-second; redeploys complete in under a second. Knative serving adds scale-to-zero and automatic burst scaling, and the workflow supports live edit-save-refresh development plus dependency flags for AWS, files, or custom libs.
AI-written summary · about
chapters (11)
- 0:00Introduction and speaker intro
- 1:12What is Apache Camel
- 5:02Quarkus and its benefits
- 9:17Demo: Camel Quarkus live coding
- 13:08What is Camel K
- 18:47Use cases for Camel K
- 19:29Demo: Camel K on OpenShift
- 24:12Serverless with Knative Serving
- 27:04Benefits of serverless integration
- 29:14Camel K with Knative integration
- 35:27Q&A and closing remarks
related talks
51mWriting Serverless Applications with Quarkus and Knative
52mContainerless, Bloatless, YAML-less, Serverless Java #slideless
43mCloud Native My Camel: from Low Code to Pro Code, inject Serverless & Cloud Native Goodness...
49mJava Patterns and Practices for Serverless Applications
30mSupersonic Java Quarkus with Knative serverless
36mServerless-Native Java with Quarkus
53mDissecting Serverless Enterprise Java Applications #slideless
55mQuarkus brings Serverless to Java developers