Learning Library

← Back to Library

Scaling Kafka Event Endpoint Management

Key Points

  • Use the AsyncAPI specification to formally describe Kafka event topics, giving them the same developer‑friendly interface and documentation standards as traditional APIs.
  • Make events discoverable through a centralized catalog with taxonomies, enabling quick search, browsing, and access to their specifications similar to an API developer portal.
  • Provide decentralized, self‑service access so developers can independently explore, register applications, and receive usage feedback—much like browsing a Netflix catalog.
  • Implement decoupled, scalable access mechanisms that expose event topics without tightly coupling to underlying infrastructure, ensuring robustness and flexibility in larger architectures.

Full Transcript

# Scaling Kafka Event Endpoint Management **Source:** [https://www.youtube.com/watch?v=-vSdDHxKVYU](https://www.youtube.com/watch?v=-vSdDHxKVYU) **Duration:** 00:06:29 ## Summary - Use the AsyncAPI specification to formally describe Kafka event topics, giving them the same developer‑friendly interface and documentation standards as traditional APIs. - Make events discoverable through a centralized catalog with taxonomies, enabling quick search, browsing, and access to their specifications similar to an API developer portal. - Provide decentralized, self‑service access so developers can independently explore, register applications, and receive usage feedback—much like browsing a Netflix catalog. - Implement decoupled, scalable access mechanisms that expose event topics without tightly coupling to underlying infrastructure, ensuring robustness and flexibility in larger architectures. ## Sections - [00:00:00](https://www.youtube.com/watch?v=-vSdDHxKVYU&t=0s) **Managing and Scaling Kafka Events** - The speaker outlines how to describe, catalog, and discover Kafka event topics using AsyncAPI specifications to enable scalable event endpoint management. ## Full Transcript
0:00have you been using kofka and been 0:02really excited about the progress you 0:04were making but wondering hey how can I 0:06scale this usage out on a much larger 0:09scale well if so you're going to love 0:11our topic today on event endpoint 0:14management hello my name is Jamil Spain 0:17IBM developer Advocate and brand 0:19technical specialist in the US Financial 0:22Services Market to cover the topic of 0:24event endpoint management I wanted to 0:27bring out four major tips that you can 0:29use use to which really encompasses the 0:32discipline of describing and managing 0:34your event topics here so we're going to 0:37start off by filling these in and we'll 0:38discuss these points as we go the first 0:42is 0:44that these event topics need to be 0:48described now there's a specification 0:50called the async API which is the pretty 0:54much the industry standard on how to 0:55describe events as topic or topics as 0:58events um which is industry standard 1:01here and what it really aims to do is 1:03give uh events the same comfort as we 1:06have grown to love with apis and let's 1:10face it now um developers will want to 1:13implement apis but they love to have 1:15that kind of that Swagger interface that 1:17they can quickly go ahead and and start 1:19to go which brings me to my next Point 1:23events should 1:27be discoverable 1:30and what this entails is uh kind of the 1:32catalog format of having all the events 1:35in one place tag with a taxonomy so it's 1:39easy for me to search and and cataloged 1:41and and very presentable for me to 1:44actually go in and read the 1:45specification for again another great 1:48Trend that we're used to for a lot of 1:50API developer portals the fourth we're 1:53going to say is you should have 2:03so I'll say that you'll have 2:05decentralized access here so what this 2:08pretty much says is people should be 2:10free to explore all right they 2:12Innovation usually comes um where I'm 2:14I'm free to kind of go out and and use 2:16it at my own Comfort I kind of 2:18equivocate it to like when I'm on 2:20Netflix and I get to browse the catalog 2:22and really find movies as I want to go 2:25kind of getting my own Rabbit Hole here 2:27some of the trends that go along with 2:29that is the capability to be 2:31self-service where I get to register my 2:33applications and truly have some way to 2:36have trackable usage on what I'm using 2:39getting that feedback there as well and 2:41the last 2:47is decoupled access so we really want to 2:51find a way that's very scalable and less 2:54fragile again the information or Kafka 2:57as a whole the the the the process of 3:00providing access to event topics should 3:03not really impede on how I'm forced to 3:06implement it here and so by putting this 3:08interface in front that would really 3:10give me a scalable way that I can expose 3:13access to this and still accomplish what 3:16I'm trying to do inside my architecture 3:18here so hopefully that describes the 3:21general Arena of managing events um um 3:24and and the things you need to pay 3:26attention to and watch out for let's 3:28move over to the right and do a little 3:30diagram about really depicting what it 3:32looks like and how it works so for this 3:35let's start out with our usual uh uh 3:38diagram that everyone knows with this 3:40how API management 3:45works and again that we we already know 3:48that apis get socialized let's say I am 3:51a user and I'm sitting at my laptop and 3:54I'm going to be looking at a developer 3:58portal we'll call that acronym that DP 4:01um and then there's the concept of a 4:03Gateway all right API Gateway 4:09and now as I browse in the developer 4:12portal I see something that I want to 4:13subscribe to Bally when I go to 4:15implement I'm going to be actually going 4:18consuming through the API Gateway and as 4:21we know it has an interface to go out 4:23and hit some other uh backend 4:27Service as is so that's a a normal 4:30practice that's that's always there 4:32again all the apis are described in the 4:34developer portal but this let's put 4:37these the these particular uh 4:39initiatives to to work here when event 4:42import management comes into play let's 4:44switch our marker here so with 4:48events we're still going to have the 4:51same developer portal 4:54here a portal that describes and list 4:57all our particular events as they go and 5:00we're also going to have the concept of 5:02a Gateway so that's called the EV the 5:05event 5:06Gateway all right so as I am still being 5:09the user let's take the same user so 5:11they're looking at apis and alongside 5:13that they have access to also browse 5:16topics here a third tier that they can 5:18do which will then as they go to consume 5:21these will go through the API Gateway 5:24and then be able 5:27to consume from from Kafka 5:31there and provide the particular 5:34information back as they would do so by 5:37using the developer portal developers 5:39get to quickly scale up and and and and 5:41be able to um look at the events that 5:44are there and know be able to test it 5:46out quickly impit and get going and as 5:48you become your Kafka become Kafka as a 5:51service or a very uh Kafka first 5:53environment where you want to expose a 5:55lot of data directly through event 5:58topics this is a great way with event 6:00endpoint management to really get that 6:02program going and facilitate that so 6:05thank you for your time hope this was 6:07very useful in your um u in your use of 6:10Kafka here and I look forward to hearing 6:12your stories about how you'll be using 6:14event endpoint Management in your 6:16architecture thank you if you have any 6:19questions please drop us a line below 6:22and if you want to see more videos like 6:24this in the future please like And 6:26subscribe