I am java backend dev from 15 years and i love it :) clean and fast, however i cannot understand some of the words especially when you are talking fast, hoping for more movies in the future
That's another great video! Congrats! And the diagrams - just awesome! Just a couple of questions: 1) What if there is no need for different microservices types, just one - just the "Pool" microservice in the presentation. Would the API gateway, as a distinct microservice, still in need in that case? Maybe it 's logic should be embedded in the single microservice type? Would that allow for multiple instances of that microservice type?(That is multiple instances of a "Pool" microservice that will have the authentication/authorization logic embedded) 2) I suppose that having huge amount of requests would lead to the API gateway to be a bottleneck - or not? If so, the API gateway should be scaled? Any advice on how going on that? Again, thanks for the amazing content!
Wow great questions! About 1: there are different approaches. One way is a "distributed monolith" kind of way. That basically means doing the same logic of the monolith but with a common database to authenticate users against. Typically this would be done with a load balancer in front of the service that can do something like "sticky sessions" (sending the request of an authenticated user always to the same server to avoid reauthenticating every time when it reaches a new server). The second approach is having the API gateway for your service. Which sounds a bit overkill but may be ok too. Both approaches of course if you want to do authentication/authorization. About question 2: definitely. The API gateway becomes a gatekeeper so it needs to scaled appropriately. These are some additional useful links: microservices.io/patterns/apigateway.html (from the book I recommend in the description) You may also read sometimes differences between "api proxy" vs "API gateway". I personally think the former is just a simpler version of the latter (with less functionality). But they both have the same issue of becoming a bottleneck. More info on that here: www.akana.com/blog/api-proxy-vs-api-gateway Hope is clear. Otherwise let me know! Really good questions!
@@ADevStory Thank you very much for taking the time to answer and also for sharing knowledge.Seems clear now but I 'll definitely spend more time on this, given the resources you suggested. Thanks once more!
Glad you liked it! I've never worked in that area though. I have some notions and can read more about it but don't feel confident about talking about it at this time 😔
Glad it was useful! Yes of course, in terms of resources, from the video description section, these are my recommendations: Resources: 🔖 FREE: - What is Cybersecurity? www.ibm.com/topics/cybersecurity - Good video on overall security basics: ruclips.net/video/xPlmRSWqSso/видео.html 📚 Paid (personal recommendations - not sponsored, but I can get some commission if you buy them through the links below, at no additional cost to you): - Api Security in Action: amzn.to/3NOgRC4 - Microservices Patterns: amzn.to/3atqjg5 - Microservices security in Action: amzn.to/3OoEPEN
![Summer Walker - Heart Of A Woman [Official Lyric Video]](http://i.ytimg.com/vi/SFddctbZzw8/mqdefault.jpg)
Thank you for the best and easiest explanation ever.
Oh thanks for the feedback! Glad it was useful!
Love your videos! This is something really valuable for learning system design which is not easy!. Thanks!
Thanks ! That's the idea! Glad you found it useful!
I am java backend dev from 15 years and i love it :) clean and fast, however i cannot understand some of the words especially when you are talking fast, hoping for more movies in the future
Thanks! I'll try to go a bit slower next time and improve pronunciation. Have you also tried the captions? I make sure those are polished
Super helpful - Thank you so much !! #StayBlessednHappy
Glad it was useful!
I love your vedios!! If you can make a new series on security implications on the different architectures, that will be fanatastic
Thank you! Glad you liked it! I'll think about it!
OAUTH is authorization protocol, it probably uses SAML/OpenID in combination with OAUTH
Great video! Thanks
Glad you liked it!
That's another great video! Congrats! And the diagrams - just awesome!
Just a couple of questions:
1) What if there is no need for different microservices types, just one - just the "Pool" microservice in the presentation.
Would the API gateway, as a distinct microservice, still in need in that case?
Maybe it 's logic should be embedded in the single microservice type?
Would that allow for multiple instances of that microservice type?(That is multiple instances of a "Pool" microservice that will have the authentication/authorization logic embedded)
2) I suppose that having huge amount of requests would lead to the API gateway to be a bottleneck - or not?
If so, the API gateway should be scaled? Any advice on how going on that?
Again, thanks for the amazing content!
Wow great questions!
About 1: there are different approaches. One way is a "distributed monolith" kind of way. That basically means doing the same logic of the monolith but with a common database to authenticate users against. Typically this would be done with a load balancer in front of the service that can do something like "sticky sessions" (sending the request of an authenticated user always to the same server to avoid reauthenticating every time when it reaches a new server).
The second approach is having the API gateway for your service. Which sounds a bit overkill but may be ok too. Both approaches of course if you want to do authentication/authorization.
About question 2: definitely. The API gateway becomes a gatekeeper so it needs to scaled appropriately.
These are some additional useful links: microservices.io/patterns/apigateway.html (from the book I recommend in the description)
You may also read sometimes differences between "api proxy" vs "API gateway". I personally think the former is just a simpler version of the latter (with less functionality). But they both have the same issue of becoming a bottleneck. More info on that here: www.akana.com/blog/api-proxy-vs-api-gateway
Hope is clear. Otherwise let me know!
Really good questions!
@@ADevStory
Thank you very much for taking the time to answer and also for sharing knowledge.Seems clear now but I 'll definitely spend more time on this, given the resources you suggested.
Thanks once more!
Thank you!
Thank you very much, Can you please give som examples about time critical applications like motor control?
Glad you liked it! I've never worked in that area though. I have some notions and can read more about it but don't feel confident about talking about it at this time 😔
Thanks, that help for AI machine maintenance research i do.
That's great!
Find your video quite helpful, do you have any good course or youtube video suggestions in mind that goes into this in detail using JAVA framework
Glad it was useful! Yes of course, in terms of resources, from the video description section, these are my recommendations:
Resources:
🔖 FREE:
- What is Cybersecurity? www.ibm.com/topics/cybersecurity
- Good video on overall security basics: ruclips.net/video/xPlmRSWqSso/видео.html
📚 Paid (personal recommendations - not sponsored, but I can get some commission if you buy them through the links below, at no additional cost to you):
- Api Security in Action: amzn.to/3NOgRC4
- Microservices Patterns: amzn.to/3atqjg5
- Microservices security in Action: amzn.to/3OoEPEN
I like your video but by no means this is security basics
Thanks! What do you think would have made it security basics?