API Gateway explained

This video will walk you through the features and use cases for an API Gateway.

[SashaPshenychniy]

Nice idea of presenting information with that glass board and luminescent markers, but for this kind of scenes Manual Focus mode on your camera would work much better - just set it once and don't touch =).

[slraja]

Wow, one proper video about API gateway without beating the bush !! hard to find such clear explanation on this topic .

[Mo.Faried]

Man you are awesome and your studio style and lighting is awesome. It got me concentrating for the longest period. The only thing I would recommend is to turn off autofocus and manually adjust it once.

[yzraeu]

I really liked the content and the way you presented. Great Work!


But you need to fix this auto-focus thing.

[Luke_]

Great explanation. I'd just like to add that a "single point of failure", in my opinion, is not really a drawback. Because if a monolithic application crashes, it's also a single point of failure. With microservices, there's a chance that only a service crashes and everything else keeps running.

[colinrickels]

Dude these videos are awesome. No beating around the bush. I like it

[PabitraPadhy]

Explained really well.
Only thing that's disturbing is the camera focus going haywire.
If you are using DSLR, then adjust the camera to focus on a single plane, or if you are using phones to record, there's also an option to lock your focus.
Videos are really helpful.. thank you :)

[PauloSilva-umwl]

you earned a new follower, it was the first video that I watched in your channel but it was an amazing time, it helped me to implement an API gateway at my job. I proposed use one to create a scalable architecture but I was finding some problems to implement it using nodejs, so now it's more clear how to solve this challange. Thanks guy

[rpesc]

Great video man, future videos perhaps consider turning the auto-focus off.

[mdrakic]

Great video that explains very easily the API Gateway purpose.

However, I would strongly advise against implementing the Orchestration/Business Logic (BL) in the API Gateway, how much tempted you might be. Create a BL layer between the API GW and the different Microservices, in that way you cleanly encapsulate that functionality in a separate module (microservice) and let the GW strictly do GW stuff. It will also make the load balancing, and future maintenance, easier since that functionality resides elsewhere. Clean and neat separation of concerns and responsibilities; future proof solution. Trust me, thank me later.

Keep up the good work 👍🏼👏🏼

[hyaenas]

Excellent video. That's how new solutions should be explained.

[SanjayKumar-bmrj]

Became a fan of your presentation, very clear and basic explanation. Just like someone has read whole chapter of an interesting book and giving concise gist of the content. Looking forward for more videos on this. Would you be able to get an tutorial on api gateway end to end.

[barsvelioglu]

Thanks for your explanation. 'Request/Response Transformation' seems better naming instead of 'Query Transformation'

[raghurajvenkatapur]

Wonderful explanation of Api Gateway Concept

[kiranshetty]

Superb explanation . Worth watching and thanks a lot .

[eutitiaj]

Wonderful and amazing explained with specific details. Thanks for sharing your knowledge.

[rjanardhanan]

loved this - very articulate and exhaustive

[virendrathakur]

A very unique way of presenting. Good work and it was really helpful. The video was going blur in between so you may want to check out to avoid this.

[ericsunkel]

I absolutely loved this video and the simplicity. You created a fan brother!

[georgiofryxell]

This is an example of "just add another box or layer" without clearly understand or explain why. As other commenter said, it has the same "single point of failure" the mono application, then why do we need this?

What happen if you combine the API Gateway with your Web application? it provides the same benefits, in this case you only expose the IP of your web, why do you need to expose the IPs of your services?

One key element for microservices design is to provide partial operation, meaning if one service down, the app is still running, by your implementation, I see if 1 service down, the whole app down.

It is a different story if you have a mobile application when the app is running on a "external" device. The the API Gateway makes sense, but normally, you can't reuse the same gateway you build for web.