However, how do you enable this new audience to get access to your streaming data? It’s not feasible, nor is it desired to expose internal channels, such as Kafka topics, externally. One could build custom applications with hand-crafted logic to enable access, but this is not without its own drama, from adapting to changes in the data, to signing on new users to the service.

So, how can we, in a relatively short amount of time, build something that will allow us to serve up consumable streaming data, with the flexibility to not only keep internal and external systems separated, but also manage security and access?

By using API management as part of your streaming architecture, you will be able to achieve just this. In addition, API management offers many other advantages, such as:
- Lock down endpoints with appropriate, modern security approaches
- Work with access policies shape and control how often and when your API can be called
- Modify the data in-flight both for incoming events, as well as outgoing ones

In this talk we will look at API and access management, how they work together, as well as discuss in detail what API management will enable you to do when it comes to event-based information exchanges.