>> Hey friends. Azure Functions and API management,
they go together like peas and carrots,
and with the recent release,
so the consumption tier for Serverless,
API management is now the best way to manage your serverless APIs.
Mike Brzezinski is here to show me
the latest updates today on Azure Friday.
[MUSIC]
>> Hey folks. I'm Scott Hanselman
and it's another episode of Azure Friday.
I'm here with Mike. How are you, sir?
>> Very good. How are you?
>> I'm glad to see you because you're going to bring me
all the new stuff that's happening in this space.
>> That's right. Today we're going to talk about
three major areas of updates on Azure and API management.
First of all, we just
released the consumption tier of API management,
it just become available in the last week of May,
and it's a fully serverless tier which is unlike
all the other tiers of
API management up-to-date which are dedicated.
These oldest the rest properties like billing prosecution etc.
Is just their consumption,
Tier for Azure Functions.
>> Okay.
>> Now, there is no excuse for you not to use API management,
if you're a beneath serverless APIs.
Also, we shall rethink Azure Functions into
a building with us diverse API for Azure functions.
API management is now a way of exposing
your OpenAPI definition of your function's applications.
That feature is not provided natively in functions version tool.
So you need to use a camera for that.
>> Okay.
>> Lastly, we have emitted there is simple for you to front
your Azure Functions Applications of
API management right from digital portal.
This what I would like to show you first.
>> Fantastic.
>> I have my function up here in the Azure Portal.
It's an unofficial, Azure File API Application.
>> We'll make it official after the shell.
>> It has two methods, episodes and people.
Now, I would love to expose it through API Management.
So to do that, I can go to platform features,
click on" API Management" right here.
This is the interface or I
confront my Azure Functions up with API management.
So to do that, I can select my API Management instance.
For example, Azure Friday and create exposit as a new API.
A constant enabled the same application Insights logging
across in the same application says instance.
>> Okay.
>> Now, you can start up all the functions are told they have
to import and confirm.
This opens the API Management viewer into functions interface.
So we are still in Azure Functions.
I can change the display name, Azure Friday API.
The suffix for the URL path.
I can also change the description of my API to,
why don't we call it the offshore.
>> We'll make it official this moment.
>Azure Friday API.
>> I love it
>> Create.
>> Okay.
>> So that's how easy it is to
expose your function through API Management.
We need to wait a few seconds until it loads,
and what it presented with InDesign viewer for your APIs.
>> This is one of my favorite, thanks
the design here is really nice.
>> Yes, but you are still in the Azure Function Interfaces,
and we loaded the API at an interface in Azure Functions App.
Now, I cannot call it for example, economic policy,
which is a course policy,
and I need to add it because,
I need just for the other part of the demo.
So I will enable course on my serverless API, and saved.
So that's the first area of
updates around the building serverless APIs.
The second area is that we made it really simple for you to
enrich your API definition with data model objects.
So you can now generate a data model object schema,
and put it into your IPA definition.
Not only it benefits you as an API provider,
it makes things simpler for you,
but also the API consumers,
your customers or the
application developers that rely on your APIs,
they benefit from it as well.
So to do that, I'll go to
the test console still in the functions view.
I will go to the test console and test name Get People Method.
So I will try to fetch
a person with the IDs cut from a serverless API.
>> Okay.
>> Let's see what I get in the return. Okay, I've got 200.
>> Cool.
>> The response is,
Scott Hanselman favorite product Azure API Management.
>> Which is very true.
>> I think that's right.
>> Yeah.
>> So as you can see, my API is working.
Now, I can generate a definition of that object.
>> So from my sample,
just from testing the API,
I can enrichment my API definition.
As you can see,
I can provide a name for it.
For example, people object,
and it will contain this sample.
But it also contains
automatically generated definition of the object.
So you can see firstName,
is defined as a trend.
So as LastName and so is favorite product.
I can save it as part of my response.
That's it. I just nourishment API.
Now coming back to what I mentioned earlier,
API management is a way of downloading or
publishing pure OpenAPI definition for Azure Functions.
So conclude this button here
to download and the OpenAPI and definition.
>> This standard is consumed
by all tools you can generate things for that?
>> Yes, all third-party, first-party tools everywhere,
is just a very common standard out there in the developer world.
So this is the JSON documentation stronger Version 2 of my API.
If I scroll down toward the Get People Method,
as you can see it contains
a schema which references to an object which is defined below.
It also contains the example.
So actually the response that I
got was automatically put into the schema.
So now, developers can build applications know
what they can expect from this API operation.
They spell this type of an object and this is an example,
and the schema is located at the end of the file.
>> That's really clever to have taken the example that we got,
and then used it as an example and generate, almost documentation.
>> Exactly, just to make it smoother for the API consumers.
The last thing that I would like to talk about is,
we have just released
a preview version of the new developer portal in API Management.
If you're not familiar with the concept of a developer portal,
it's an automatically generated websites.
Whether the documentation or APIs.
Typically, API consumers go to
the developer portal to learn about the APIs,
discovered them, and then finally get
access to them and build applications that use those APIs.
The new portal is competitive built from scratch.
It is re-imagined compared to the old developer portal.
I can launch it right from
API Management instance from the Azure Portal,
and this is the administrative view that's loading up.
>> Right.
>> I don't have enough time to go through
all the functions of the developer portal,
but this is the default landing page that you can fully customize.
>> Wow.
>> Now, I will open
the developer portal in a incognito browser mode.
So I will open it as an actual [inaudible] as an administrator.
Now, I can explore the APIs that
are part of my IPA Management Instance.
As you're going to see there's Azure Friday API here,
and there can see all the API operations.
I go to "Get People" I can open the interactive console,
the Contonso console that we saw on the administrative side.
It's also therefore the API Consumers.
People who build applications with the APIs.
I can call it the same way I call it from Azure Portal,
and I would get the response here as well.
>> That's cool.
>> Also, the new developer portal is completely open source.
It's available on in a GitHub repository under the URL API.MS.
Search API in the portal.
>> Yeah.
>> Should go there. You can see
the GitHub repository with the source code of portal.
>> So that's the source code of
the portal ledge is generated for you?
>> No, that's the source code of the portal codebase.
So if you're a customer,
and let's say the developer portal
that we provide is not enough for you,
you can extend it however you wish.
You can have some developers work on it
implement in the custome features that are needed for you, by you.
Yeah, then self host your own developer
portal outside of your API Management instance.
>> That's so cool. So if you modify the
portal and run it yourself in Azure is its own website.
>> Yeah.
>> Does it then call over to the,
>> Exactly. So the one that
we saw was provided with API Management Instance.
But if you will require extensions,
you can build your own developer
portal outside of API Management Instance,
and it still connects to API Management Instance.
>> So it's not that you generate a portal.
>> Yeah.
>> You also calling to the backend for
the authoritative API and building.
>> Exactly.
>> Wow it's nice.
>> Yes, so that's not for the advanced users,
and hostilities super simple,
all you need is just a storage card.
So you can code on
your local machine and the charts damned HTML files,
the storage account and that's it.
>> Oh, really. So it's entirely client type?
>> Yeah, it's all static pages,
HTML pages with JavaScript.
So all the information that is dynamic is first on
the client side from the browser is in JavaScript.
>> That is a really lovely upgrade in Open-source group.
>> Exactly. Not only the developer portal code is Open-source,
so are the issues,
documentation, and also the product roadmap.
Map roadmap which will keep updating. Its currently in preview.
The GA is planned for October-November timeframe.
That's all of the updates that I wanted to share today.
>> That is really extraordinary,
and what a clean bit of architecture there that really puts
the customer in charge of
their APIs and it just makes things very nice.
There's really no excuse. If you've got a nice developer API,
get the people a nice portal for it as well.
>> Exactly. We want to empower you to create an application today,
and create any solutions that you want.
>> Fantastic. Well, thank you for sharing.
>> Thank you very much.
>> I am learning all about some of
the great new API Management features today, on Azure Friday.
[MUSIC]