mixing up api gateway and stand alone apps that orchestrate worklows, services for speciic tasks like buy an ice cream. api gate way - hide changes in implementation, do rate limiting etc. Could be part of same process or another process. but logically different.
So refreshing!! I started a Computer Programming Course and have been researching the different areas of Coding etc. I came across the concept of the API and trying to understand how it fits into modern Internet-user-Appication infrastructure. Yours is one of the best explanations I've seen for a while!! Great job!!
You can use different versions for your services as they are changing. Even gateway api will have to go through versions if you are changing things. Create a nuget package to identify requests for all the services.
I enjoyed your explanation. What about in the case where I want to expose my APIs to 3rd parties and not my _own_ frontends....does the API gateway handle metering and billing for an API key? If you can do a video of an example of how this works, I'd appreciate it.
What do you mean by metering? For 3rd parties it is even more advised. If you have your own application that communicates with your servers it is easier to change it once your servers change. It is much harder to ask the 3rd party to change something because you are changing your servers. With API gateway you can change your servers behind it without changing the API exposed to the 3rd parties
@@ProgramArtist Thanks for the response. Basically, I want to publish an API that I can _sell_ to 3rd parties. For example, suppose I have an API that computes cancer risk based on some input biomarkers. I want to expose this to healthcare insurance companies. I want to charge 10 cents / .1 USD per invocation of my API. Can API Gateway (like AWS API Gateway or others) handle this for me?
@@VishalRaoOnRUclips The AWS API gateway is more of a pure API gateway, it is pure in a sense it just redirects the request based on some rules (it doesn't apply any logic). So the logic of billing should be done by you.
That's exactly what I wanted to know. It's not that making a REST that sits between the user and your other services is a bad idea. It makes perfect sense. I'm just wondering how API gateway is different than say, deploying a REST api with Spring Boot onto an EC2 instance. Does it dictate that you use lambda? Can you use EC2 or ECS? What does it offer?
It depends on how simple you want it to be. You can use some built-in service that the cloud providers have like AWS API Gateway or similar products from Azure or Google Cloud. You can also use NGINX to setup one which is even more sophisticated or you can develop a service on your own. It really depends on your needs. I would suggest not developing one on your own but using an existing product
I like the workflows.. can you show us how to actually connect to a web app or any of these things using something like aws lambda.. where do we input the end points.. the JavaScript?
I'd put it in another service, the API gateway would call it as a first thing, get the needed tokens/user information with access rights and stuff like that and with that information call the other services.
Complex logic shouldn't go in an API Gateway. The service's single purpose is to buffer the external API (what the clients use) from the internal API (service layer API's). Complex logic brings 'business logic' to mind and should be housed in a separate microservice
Let me know what would you like me to talk about, it can be anything as long as it is programming related
Choreography patterns, please!
Why not step by step process of setting up the "Api Gateway".
EXCELLENT TUTORIAL ............. one question
Where to put the Authentication & Authorisation ? In API gateway ?
mixing up api gateway and stand alone apps that orchestrate worklows, services for speciic tasks like buy an ice cream. api gate way - hide changes in implementation, do rate limiting etc. Could be part of same process or another process. but logically different.
Please tell about web hooks.
Best Explanation of API Gateway i have found on the web , just 5 minutes on the video and i already understand it thank you for sharing your knowledge
So refreshing!! I started a Computer Programming Course and have been researching the different areas of Coding etc. I came across the concept of the API and trying to understand how it fits into modern Internet-user-Appication infrastructure. Yours is one of the best explanations I've seen for a while!! Great job!!
great explanation i have been try to figure this out for a while now thank you :)
Wow I cant believe I learnt so much in just 20 minutes (10 if you watch at double the speed)
a more detailed piece of code on this api gateway would be helpful, so what happens exactly when the gateway receives an order.
You can use different versions for your services as they are changing. Even gateway api will have to go through versions if you are changing things. Create a nuget package to identify requests for all the services.
Thanks for putting time into this video! It was helpful!
I like u buddy lol... the background music.. the casual small whiteboard lol... this is not geek at all, very funny haha but super useful! Thank you!
Please remove the background music, it is a hinderance to hearing and learning.
I enjoyed your explanation. What about in the case where I want to expose my APIs to 3rd parties and not my _own_ frontends....does the API gateway handle metering and billing for an API key? If you can do a video of an example of how this works, I'd appreciate it.
What do you mean by metering?
For 3rd parties it is even more advised.
If you have your own application that communicates with your servers it is easier to change it once your servers change. It is much harder to ask the 3rd party to change something because you are changing your servers. With API gateway you can change your servers behind it without changing the API exposed to the 3rd parties
@@ProgramArtist Thanks for the response. Basically, I want to publish an API that I can _sell_ to 3rd parties. For example, suppose I have an API that computes cancer risk based on some input biomarkers. I want to expose this to healthcare insurance companies. I want to charge 10 cents / .1 USD per invocation of my API. Can API Gateway (like AWS API Gateway or others) handle this for me?
@@VishalRaoOnRUclips The AWS API gateway is more of a pure API gateway, it is pure in a sense it just redirects the request based on some rules (it doesn't apply any logic). So the logic of billing should be done by you.
great expalanation, thanx for great example
How is API different from any middleware product?
That's exactly what I wanted to know. It's not that making a REST that sits between the user and your other services is a bad idea. It makes perfect sense. I'm just wondering how API gateway is different than say, deploying a REST api with Spring Boot onto an EC2 instance. Does it dictate that you use lambda? Can you use EC2 or ECS? What does it offer?
Excellent...simple and relevant.
Very informative. Thanks. It took me back to the old classroom days when teacher used to explain concept on black or whiteboard.
Hi can you please explain how to setup an API gateway? is it provided by some vendor ? thanks
It depends on how simple you want it to be.
You can use some built-in service that the cloud providers have like AWS API Gateway or similar products from Azure or Google Cloud. You can also use NGINX to setup one which is even more sophisticated or you can develop a service on your own. It really depends on your needs. I would suggest not developing one on your own but using an existing product
ProgramArtist thank you so much for the reply, Netflix is also having an existing API Gateway right?
@@diegoramos27 I don't really know, but I imagine they do
Great explanation!!
I like the workflows.. can you show us how to actually connect to a web app or any of these things using something like aws lambda.. where do we input the end points.. the JavaScript?
U r great dude.
Please come again!
EXCELLENT TUTORIAL ............. one question
Where to put the Authentication & Authorisation ? In API gateway ?
I'd put it in another service, the API gateway would call it as a first thing, get the needed tokens/user information with access rights and stuff like that and with that information call the other services.
can you do advaned angular app like that has modular architecture?
awesome video ! Thank you !
Wow, great video. I’ve a doubt: we have a web app (aspnet mvc) that needs to connect to a database only. Should I add an API gateway in this scenario?
Your web-app should never connect the database directly. You cannot safely connect to the database from a web browser
Great presentation!
great video! thanks
for ice cream the most important is not to use API gateway but a refrigerator
I like your T shirt.... CODE BLOODED
cool description
I think some other topics you could cover that could get some views is Spark, Blockchain and Machine Learning, they're hot topics.
It was going really well until you said lets put complex logic into API Gateway.
could you explain..?
Yes. Sliout, please explain
Complex logic shouldn't go in an API Gateway. The service's single purpose is to buffer the external API (what the clients use) from the internal API (service layer API's). Complex logic brings 'business logic' to mind and should be housed in a separate microservice
helpful
why take so much time to come to the topic....?
Except aws u said all things
Super slow explanation, unnecessary!
Great video! thanks