Overview

With Kyma Eventing, you can focus on your business workflows and trigger them with events to implement asynchronous flows within Kyma. Generally, eventing consists of event producers (or publishers) and consumers (or subscribers) that send events to or receive events from an event processing backend.

The objective of Eventing in Kyma is to simplify the process of publishing and subscribing to events. Kyma uses proven eventing backend technology to provide a seamless experience to the user with their end-to-end business flows. The user does not have to implement or integrate any intermediate backend or protocol.

Kyma Eventing uses the following technology:

• NATS JetStream as backend within the cluster
• HTTP POST requests to simplify sending and receiving events
• Declarative Subscription CR to subscribe to events

Kyma Eventing flow

Kyma Eventing follows the PubSub messaging pattern: Kyma publishes messages to a messaging backend, which filters these messages and sends them to interested subscribers. Kyma does not send messages directly to the subscribers as shown below:

Eventing in Kyma from a user’s perspective works as follows:

• Offer an HTTP end point, for example a Function to receive the events.
• Specify the events the user is interested in using the Kyma Subscription CR.
• Send CloudEvents or legacy events (deprecated) to the following HTTP end points on our Event Publishing Proxy service.
  • /publish for CloudEvents.
  • <application_name>/v1/events for legacy events.

For more information, read the Eventing architecture.