How to build an API Gateway in ASP.NET Core using Ocelot (Build API Gateway in a few minutes)

API Gateway is an API management tool that usually sits between the external caller (Web or Mobile) and the internal services. The API Gateway can provide multiple features like:
1. Routing
2. Request Aggregation
3. Authentication
4. Authorization
5. Rate Limiting
6. Caching
7. Load Balancing
ETC.

Ocelot is an ASP.Net Core (Supports .Net Core 3.1) API Gateway. It's a NuGet package, which can be added to any ASP.Net Core application to make it an API Gateway.
Ocelot API Gateway supports all the features that any standard API Gateway does.
I will cover the following features of Ocelot API Gateway in this video:
1. Routing (Basic routing to internal service)
2. Authentication (JWT Token-based authentication)
3. Response Caching (Using Ocelot.Cache.CacheManager NuGet package)
4. Rate limiting

[ramsys]

Superb Presentation. What I like the most was the "style" in which you presented.... crystal crisp clear voice, no high or low pitch in your voice, going at constant steady speed, up to the point explaining each step properly, no shuffling from one screen to another (its very irritating) which makes to loose link. Looks like you have taken pains to plan your presentation well in advance keep up with the good work.

[nguyenminhat]

I'm beginning to learn Microservices. Thank you so much for this video. It's very helpful for me :D

[nageshs]

Awesome explanation. Entire source code is also shared. Up voted. Keep up your good work sir.

[umeshkushwaha]

Very well explained. I appreciate your effort Nirjhar. It was honored to work with you.

[savithapn]

Great presentation, i like the way you explain any hard topic in a simple way so that anyone can understand, keep up the good work !

[talhatariq]

Greatly Explained! Kindly I request to Create a PlayList on API Gateways. Regards

[shriji]

Question: Can you please explain or extend this example with Kubernetes please? I found this helpful and I have implemented the same with Docker (docker desktop) but couldn't find much materials to extend in kubernetes.

[mahendranchinnaiah]

Great Job.. I like to watch all of your videos. Please try some concepts in cloud environment(AWS, Azure)

[pt_trainer]

Very concise tutorial, thank you.

I added a Middleware in my individual services to check for a specific header that I only set at the gateway level so that clients cant call my microservice endpoints directly, but only through the gateway.

Is there a better way to handle this for local dev. (Not using NSG in Cloud Service etc)

[rajeshhsp]

to the point and precise. thank you for this.

[sreedharcb]

great video!, explained in simple steps. Thank you :)

[Aweklin]

Thanks a bunch for this video. It's now clearer to me how to use it.

[channing]

Thanks for the video ! Actually the keys are different in two videos ("This is my test key" vs. "Thisismytestprivatekey"), maybe that's why some people fail the test :D

[hannesbergsten]

Awsome video, I will try this tomorrow. Thanks alot!

[RAM-ffdy]

I always wait for your videos., , great stuff..Really appreciate all your efforts..waiting for videos on Azure service bus, Azure Functuons, Azure MessageQueueing, Azure App Insights...etc

[RameshKumar-grdt]

Thank You Sir.. This is really great video.

[amitbajaj]

Hi, Which Opensource API gateway would you recommend for heavy load, several applications and microservices. ?

[FurqanaFathuzzaman]

This is an awesome video!

I have a question, though. Where or how the gateway find the authentication server? I didn't see you state the address (localhost:5030) anywhere

[kalyankumarsubramaniyan]

thank you very much for your video. Please do a video for certificate based authentication

[govardhanm]

Good explanation Nirjhar, about the concepts.

If possible share the related links in creating Authorization token (JWT) project in Description. Thanks.