Requests go directly to servers, as determined by the load balancer. Could you describe what you mean by loosely coupled?
Requests are asynchronous. You can start a request and finish it in separate steps. I also don't understand what you are looking for here. Could you clarify what you want? On Tuesday, February 14, 2017 at 12:55:21 PM UTC-8, [email protected] wrote: > > I'm setting up a microservices architecture, and am confused about how > gRPC can loosely-couple services (compared to a pub-sub message service > like Kafka or Google pub sub). > Doesn't the request go directly to the server, and not through a pub/sub > system? > I read that gRPC supports asynchronous requests, but should I still use > pub/sub as a buffer between services to scale them independently and > provide for queuing? > > thanks, > imran > -- You received this message because you are subscribed to the Google Groups "grpc.io" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/grpc-io. To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/09531bed-c51f-4172-87ee-e38ee9bdaac6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
