Kong Kong Demos, 17 Oct 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Kong Developer Portal Overview | Kong Summit 2020

Description

Learn more: https://bit.ly/3lUfuUC

The Kong Developer Portal provides a single source of truth for all developers to locate, access and consume services. With intuitive content management for documentation, streamlined developer onboarding and roles based access controls (RBAC), Kong’s Developer Portal provides a comprehensive solution for creating a unified developer experience. To take your developer experience to the next level, customers can customize the developer portal to reflect their organization’s unique branding.

A

Hello and welcome once again to the demo booth. My name is ahmad koshok I'll, be taking you through an overview of the kong developer portal, which is part of the kong platform.

A

The con platform is used by organizations to decentralize and distribute their applications by creating apis and microservices. The platform helps them secure these apis and microservices and deliver them in a well-governed manner. The final component of the platform has to do with productizing these apis and making them available for external users and consumers.

A

Now this is not a trivial matter. Typically, external users and consumers need a bit of assistance to quickly and easily discover the apis that they need to use them to test them, and this is the intention of the developer portal. The key features of it is to help with this challenge of regulatory and reliably publishing api specifications, allowing external users to browse and search those specifications, perhaps test them out and finally, to do their own credential management such that the overhead of this task is not a big one on those running an api gateway.

A

So we'll take a look at a brief demonstration where we cover a couple of areas. Firstly, how easily can we publish those apis, the faster we can publish the apis, the more consistent and up-to-date? We can keep our documentation, therefore, we'll see how this is possible within the designer tool that we've showed before, as well as discuss how this can be automated.

A

Secondly, we'll take a look at once. Those apis have been published how external consumers can browse them and try them out, and finally, we will also show how external consumers can manage their own credentials.

A

Let's go ahead and go to the portal, and immediately you see that we only have one specification available to us and right now, it's branded with all the con colors but, of course, organizations alter this all the time to suit their own needs. But, let's assume we want to publish another specification. How can we do that? If you recall the designer tool that we used previously lets us view all the specifications that we have here from the same tool, we can publish apis.

A

And after we specified the parameters for connectivity to the portal, we gave the api specification a name and let's go ahead and upload it, and we get a message that it has been successful.

A

Let's go back to the portal to verify that our publishing has been successful.

A

And here we are, we can see that the new specification has been published if we want to automate this. As I mentioned, we use the command line interface to accomplish the same requirement that I accomplished using the designer here very well. Let's now take a look at how a developer might browse, find, locate and try out apis.

A

If you take a look at the portal, we can see all the specifications that have been published here on the homepage. Of course, we can make those only available once someone has logged in, but even then you can imagine how. If we have maybe a dozen or more specifications, it can be quite cumbersome to locate the apis that we need. This is why we have an online catalog where developers are able to search for apis by name, for example.

A

If I want to find something that has to do with pets, it automatically filters for me the specification that has to do with pets.

A

We also can filter based on categories which are related to the tags within any one of the specifications and when we do that, the same filtration mechanism allows us to zero in on the api specification that we need. Let's go ahead and try this one out.

A

If you recall from the designer, when we were building the specifications, we had a preview notice, how this looks identical to the preview that we saw external developers are also able to try out the apis. So let's do that here for one of the apis- and this is purely an example so that the developers can see what the response that they will get back in, but they also are able to have a code generated for them so that they may try this in their own applications.

A

This is convenient for external developers because it makes their job that much easier and, of course, we can here support other languages on demand.

A

Now, let's take a look at how developers may also manage their own credentials, so they do not become a burden every time they need to create a new api key. Let me log into my own account and show you how I do.

A

A

As you can see in my home page, I have the ability to create one or more credentials that I will use to access services that I'm entitled to so in this case, I will simply create an api key, and I can use this key in my own application and I can definitely delete this key. You may also notice how I have access to some more information and some more documentation that wasn't available to a developer that logs into the portal.

A

So let me exit out of here very well, so we covered three features in the developer portal: how we can publish apis both manually and automatically, and how this improves the quality with documentation by keeping it up to date, how external developers are able to easily locate apis so that they can get to to run their applications faster rather than asking for support and help? And finally, once again, how can they they can manage their own credentials?

A

So they don't become a burden on the operators of the common platform every time they want to alter an api key or other credential mechanism they have, and that is all thank you. So much for watching this brief demonstration, and I wish you much success as you use the comp platform goodbye.