Would you prefer using gRPC and let the frontend call individual services or building an API gateway? There is a lot of pros/cons on both solutions. I like more the Idea of control and API gateway.
Is this the case for another 'naive microservice' example: all of the services depend on each other when forming valid business transactions. In other words, we still have a monolithic app broken down on modules, but instead of relying on API we introduce a messaging layer, which is not needed for the monolithic app. Where am I wrong?
How would you recommend handling a scenario lets say you have an Active-Passive cluster where you want to ensure that only one cluster is processing the messages from the queue which is shared b/w the two clusters?
I was trying to build a message queue when I started focusing on how her smile is like Katie Holmes from Batman Begins. Stay focused my fellow men and women.
you can, of course. gRPC can be used successfully for communication between microservices. The issue is whether you want it to be tightly coupled and synchronous (gRPC), or loosely coupled and asynchronous (Message Broker).
Honestly, it mostly depends on what kind of business you are developing apps for as your solution/architecture should always consider things like scaling, load management, data persistence, etc. Even for developers that mostly work in small businesses, if you ever leave the company and interview somewhere else they will most likely want to see how you handle these types of scenarios.
Beautiful explanation whatever mentioned has been done in a crystal clear manner. Thank you
Great video! Using a high level example is very helpful.
One of the best explanation! And I watched a lot!
Thank you!
@@CloudAMQP for me too
Amazing explanation and very straightforward; thank you!
I am building my final year(BSc in CSE) e-commerce project using spring boot based on microservice architecture.
Would you prefer using gRPC and let the frontend call individual services or building an API gateway? There is a lot of pros/cons on both solutions. I like more the Idea of control and API gateway.
subscribed from the first video , very good explanation :) !
Is this the case for another 'naive microservice' example: all of the services depend on each other when forming valid business transactions. In other words, we still have a monolithic app broken down on modules, but instead of relying on API we introduce a messaging layer, which is not needed for the monolithic app. Where am I wrong?
Aaand nice explanation with a real world scenario. Thank you
How would you recommend handling a scenario lets say you have an Active-Passive cluster where you want to ensure that only one cluster is processing the messages from the queue which is shared b/w the two clusters?
Beautifully explained!!
I like ur smile ,while talking with smiling so good.final summary is nice
Nice explanation about micro svc. The msg queue need more explanation, new video would be great. Thanks!
You got it! :) We will get to work right away. Stay tuned.
Here is now a new video: th-cam.com/video/5-Rq4-PZlew/w-d-xo.html
I was trying to build a message queue when I started focusing on how her smile is like Katie Holmes from Batman Begins. Stay focused my fellow men and women.
A very good explanation indeed
Excellent, thanks.
Nice intro to message queuing
Great presentation!
This is was very well explained!
although the video is about message queue , can i use gRPC instead of message queue for the abbbove example? if yes/not then why?
you can, of course. gRPC can be used successfully for communication between microservices. The issue is whether you want it to be tightly coupled and synchronous (gRPC), or loosely coupled and asynchronous (Message Broker).
El mejor video que he visto de microservicios y colas , excelente , esa chica es guapa
The example make it easier to learn
Well explained! Thanks
Thank you !
Good explained! Thank alot
Nice explanations.
cute and good explanation
Thank you
well explained !
beautiful...
Sounds like a lot of work and complexity for something simple...
Honestly, it mostly depends on what kind of business you are developing apps for as your solution/architecture should always consider things like scaling, load management, data persistence, etc. Even for developers that mostly work in small businesses, if you ever leave the company and interview somewhere else they will most likely want to see how you handle these types of scenarios.
Lovely
thanks ...
She's so sweet man
sank yu sou much uh
omg you are cute.