Event Endpoint Management continues to be enhanced

Event Endpoint Management continues to be available and enhanced as part of IBM's integration platforms.

End of Marketing announcement for IBM Event Automation

Event Streams and Event Processing are deprecated and no enhancements will be provided. Support and security fixes will be provided in line with published support lifecycle policies. Future event-driven solutions that make use of Apache Kafka and Apache Flink will be delivered by IBM Confluent.

For more information, see the support lifecycle transition and software ordering completion announcement.

Component topology

API management systems consist of a number of deployed components. These components typically encompass a particular function or phase of the API management process. For example, an API management solution might contain:

  • Management components: where APIs are authored, policies applied, and API usage managed. In addition, governance and Day 2 operations and management activities of API usage are also managed from here.
  • Socialization components: where APIs are documented and socialized for external use.
  • Gateway components: a runtime service that exposes published APIs for clients to connect to, abstracts the service providing the API, and applies configured governance or policy rules that are enforced on clients utilizing the API.

In offerings such as IBM API Connect, the management component (API manager) enables APIs to be published to the socialization (Developer Portal) and gateway (DataPower API gateway) components to enable API adoption and use. Additional components, such as analytics processing, can also be integrated into API management solutions to provide further insight into API usage and trends as adoption grows.

Event Endpoint Management consists of two components, which together provide a similar set of capabilities to an API management solution:

  • Event Manager: where event sources are authored, controls applied on them, and they are socialized for external use.
  • Event Gateway: a runtime service which hosts event endpoints that are exposed for clients to connect to, abstracts the service providing the event endpoint, and applies configured governance or controls that are enforced on clients utilizing the event endpoint. These work together in an Event Gateway group to provide deployment, flexibility, and scaling options.

The component architecture and topology for an Event Endpoint Management instance reflects the specific requirements of an event management use case, and can expose and manage how an event source is utilized externally. However, it is possible to integrate and combine the event management capability provided by Event Endpoint Management with the API management and governance capability of IBM API Connect to enable the governance and socialization of both APIs and events in one place.

This provides event authors the features to describe and define their event sources in an event-focused manner, to socialize these event endpoints as APIs, to leverage the capabilities of the Event Endpoint Management Event Gateway to provide event-specific enforcement, and provides API lifecycle and governance management options for handling the entire organization’s APIs in one place.