From Camel to Kamelets: new connectors for event-driven applications
summary
Kamelets are reusable connector YAMLs that let event platforms like Kafka or Knative connect to 300+ systems via Apache Camel route templates and a JSON config schema. The demo installs the Camel K operator on Kubernetes, binds a Telegram source to a Knative channel, prints messages to a log sink and uses an S3 streaming upload camelet that batches into files with five-message batching. A new Beer source Kamelet is scaffolded from a random-data HTTP API and pushed to the public catalog via a pull request.
AI-written summary · about
chapters (12)
- 0:00Introduction to Kamelets
- 1:37What are Kamelets
- 4:05Why Kamelets were created
- 5:50How Kamelets work
- 7:59Using Kamelets in Camel K
- 10:26Demo: Telegram to Kafka
- 18:30Demo: Log and S3 integrations
- 24:51How Kamelets are made
- 29:40Demo: Creating a custom Kamelet
- 37:22Contributing Kamelets upstream
- 38:25Future of Kamelets
- 40:13Q&A
related talks
37mBuilding Cloud Integration Applications Through Knative and...
01h 02mModern Event-Driven Workloads with Knative
30mApplication Modernization with Camel JavaScript and OpenShift
23mKnative 101: What it is, and what it will be
25mDeclarative Event-Driven-Application Patterns with Knative
31mEvent driven communication with Kafka on Kubernetes
48mLet's Go Knative
25mKubernetes IoT Edge Working Group: Using Event Driven Architecture at Edge