Introduction

As part of your event-driven architecture solution, Event Endpoint Management provides the capability to describe and catalog your Kafka topics as event sources, and to share the details of the topics with application developers within the organization. Application developers can discover the event source and configure their applications to subscribe to the stream of events, providing self-service access to the message content from the event stream.

Access to the event sources are managed by the Event Gateway. The Event Gateway handles the incoming requests from applications to consume from a topic’s stream of events. The Event Gateway is independent of your Kafka clusters, making access control to topics possible without requiring any changes to your Kafka cluster configuration.

Event Endpoint Management architecture

Event Endpoint Management can be deployed as a standalone installation, or it can be deployed as part of Cloud Pak For Integration. You can also integrate Event Endpoint Management with API Connect by importing the AsyncAPI document that defines the Kafka event source. This integration provides the option to use events as part of your overall API management solution.

The following diagram provides an overview of Event Endpoint Management.

Overview of Event Endpoint Management.

  1. The Kafka administrator describes the Kafka topic, which is the event source. They can select a topic from an existing Kafka cluster or specify a new cluster, after which the topics on that cluster can be made available by adding and describing them.
    • Event Endpoint Management 11.1.1 icon The Kafka administrator creates options for a topic to define different ways of presenting the topic in the catalog.
  2. The Kafka administrator publishes the event source in one of the following ways depending on their version:
    • The Kafka administrator publishes the Kafka topic. The topic is then available in the catalog for application developers to discover and use as an event source.
    • Event Endpoint Management 11.1.1 icon The Kafka administrator publishes an option. The option is then available in the catalog for application developers to discover and use as an event source.
  3. In the catalog, the application developer can browse the available topics and options that represent event sources and discover information about the kind of event data available, based on which they can decide which one to use in their applications.
  4. The application developer selects the topic that provides the source of events required for their application and completes one of the following actions depending on their version:
    • Subscribes to the topic, generating the required credentials for their application to consume from the topic. The developers can manage their subscriptions through the Event Endpoint Management UI.
    • Event Endpoint Management 11.1.1 icon Chooses an appropriate option for their application to consume from. They subscribe to that option to generate the required credentials for their application to consume. The developers can manage their subscriptions through the Event Endpoint Management UI.
  5. The application developer connects their application to the event source using the snippets and credentials provided, and this sets up their application to consume from the selected topic or option through the Event Gateway.
  6. The application connects to the Event Gateway for access to the topic or option’s event stream.
  7. The Event Gateway routes traffic securely to and from the Kafka cluster that holds the relevant topic content, providing the content to the application as defined by the topic or option.