2 years ago

Category: Software, Data, Kubernetes

Applications have increasingly relied on event-driven architectures (EDAs) in recent years, especially with the advent of serverless and microservices. EDAs decouple an event from the subsequent actions that may follow, as opposed to traditional linear architectures, where an event might be processed in that same code.

Camel K, then, is an adaptation of Camel for Kubernetes that installs and manages the lifecycle of Camel via a Kubernetes Operator, he said.

We have the ability to deploy a Camel K connector, and have that essentially serve as an ingress point for Knative and serverless.

Camel K can perform what he referred to as an “event sync,” wherein after accepting some data from an external system and processing that data with a serverless architecture, it can then be routed elsewhere.