Hi @GreenLearner, is API Gateway and Sidecar proxy same? as per the architecture diagram and my understanding, when we deploy an MS, we only have a single API gateway to manage the functionalities like service discover, auth, logging etc. but as shown in diagram, for sidecar proxy, we will have a different/ dedicated api gateway and that proxy will manage only the services which are connected to sidecar my service mesh connections. ln short, the sidecar proxy will handle the service discovery of only the API/other sidercar proxy to which it is connected. is it so, or I am getting it somewhere wrong??
API Gateway is a design pattern that provides a single entry point for all incoming client requests to a microservices-based application. Sidecar Proxy, on the other hand, is a pattern where each microservice instance is accompanied by a dedicated proxy service. API Gateway provides a centralized entry point for all client requests to access microservices, while Sidecar Proxy provides a more distributed approach by providing a dedicated proxy for each microservice instance. The choice between the two patterns depends on the specific requirements and characteristics of your microservices architecture.
In Control Plane, Data Plane Diagram I observe the Following 1. API communicates with Service Mesh (SM)and vice versa. 2. Any Information/Data coming to any Instance(Microservice) comes via corresponding SideCarProxy. 3. MicroServices can communicate with each other using their corresponding SideCarProxy. QUESTION - How MicroServices GIVE response to Service Mesh, I mean is communication between ServiceMesh and SideCarProxy array is also bi-directional, which the diagram does not show? Please clarify, thanks
I think there is a bit of confusion here. If I am not wrong, you are understanding SM as a separate service which is communicating with microservices but this is not the case. SM is the name of concept/architecture which can be implemented as shown in the diagram. Sidecar proxy is one component that helps in implementing the SM. I would say, you take a look this article - www.nginx.com/blog/what-is-a-service-mesh/ Please comment back if you still have a question. BTW, I appreciate that you asked it.
@@codefarm0 Thanks, I got your point you were correct I was thinking it a ]s a separate service. I am following this series, it is a very interesting and good learning path. Great work, and thanks for the prompt replies.
@@codefarm0 This series is all about concepts. I believe to learn the Implementation part will the following help ruclips.net/video/XsaAvX86alY/видео.html&ab_channel=GreenLearner OR is there any other series that can you suggest for learning SpringBoot and MS
@@ankursaxena.melodies Implementation of some of these concepts already implemented - ruclips.net/p/PLq3uEqRnr_2Hb9M-hz6GPVg_x9TUQ9PJA All other, I'll upload as soon as it's ready
![[#2024MAMA] BIGBANG (빅뱅) - 뱅뱅뱅 (BANG BANG BANG) + FANTASTIC BABY | Mnet 241123 방송](http://i.ytimg.com/vi/EQsYfiPR9uM/mqdefault.jpg)
Complete Course Plan - github.com/greenlearner01/Microservices-Architecture
Playlist - ruclips.net/p/PLq3uEqRnr_2EDsuxPboP9_WtVRR_TaMrF
nice
Thanks
Hi @GreenLearner,
is API Gateway and Sidecar proxy same?
as per the architecture diagram and my understanding, when we deploy an MS, we only have a single API gateway to manage the functionalities like service discover, auth, logging etc.
but as shown in diagram, for sidecar proxy, we will have a different/ dedicated api gateway and that proxy will manage only the services which are connected to sidecar my service mesh connections.
ln short, the sidecar proxy will handle the service discovery of only the API/other sidercar proxy to which it is connected.
is it so, or I am getting it somewhere wrong??
API Gateway is a design pattern that provides a single entry point for all incoming client requests to a microservices-based application.
Sidecar Proxy, on the other hand, is a pattern where each microservice instance is accompanied by a dedicated proxy service.
API Gateway provides a centralized entry point for all client requests to access microservices, while Sidecar Proxy provides a more distributed approach by providing a dedicated proxy for each microservice instance. The choice between the two patterns depends on the specific requirements and characteristics of your microservices architecture.
nice video thanks @code farm
Glad you liked It :)
Is service mesh only if you have implemented a sidecar pattern?
yes
In Control Plane, Data Plane Diagram I observe the Following
1. API communicates with Service Mesh (SM)and vice versa.
2. Any Information/Data coming to any Instance(Microservice) comes via corresponding SideCarProxy.
3. MicroServices can communicate with each other using their corresponding SideCarProxy.
QUESTION - How MicroServices GIVE response to Service Mesh, I mean is communication between ServiceMesh and SideCarProxy array is also bi-directional, which the diagram does not show?
Please clarify, thanks
I think there is a bit of confusion here. If I am not wrong, you are understanding SM as a separate service which is communicating with microservices but this is not the case. SM is the name of concept/architecture which can be implemented as shown in the diagram. Sidecar proxy is one component that helps in implementing the SM.
I would say, you take a look this article - www.nginx.com/blog/what-is-a-service-mesh/
Please comment back if you still have a question.
BTW, I appreciate that you asked it.
@@codefarm0 Thanks, I got your point you were correct I was thinking it a ]s a separate service.
I am following this series, it is a very interesting and good learning path.
Great work, and thanks for the prompt replies.
@@ankursaxena.melodies You very welcome.
Glad to hear that it's helping you :)
@@codefarm0 This series is all about concepts.
I believe to learn the Implementation part will the following help
ruclips.net/video/XsaAvX86alY/видео.html&ab_channel=GreenLearner
OR is there any other series that can you suggest for learning SpringBoot and MS
@@ankursaxena.melodies Implementation of some of these concepts already implemented - ruclips.net/p/PLq3uEqRnr_2Hb9M-hz6GPVg_x9TUQ9PJA
All other, I'll upload as soon as it's ready
Is Kubernetes an example of Service Mesh ?
Extremly boring ....