1 Answers
Load balancer needed for to distribute the requests coming from the users, but messaging needed internally to communicate between services to be loosely coupled
Sign Up Free or Log In to participate!
What is the best architecture with respect to using messaging service or load balancers in order to achieve loosely coupled architecture and high availability.
In other terms, can we use Messaging service as replacement for Load Balancers or Messaging service should be used along with Load Balancers?
Load balancer needed for to distribute the requests coming from the users, but messaging needed internally to communicate between services to be loosely coupled
Psst…this one if you’ve been moved to ACG!
I really don’t understand the question. What kind of messaging service are you referring to? I’m going to assume SQS. Loose Coupling and Load Ballancers are used to achieve different things. Loosely coupled systems increase resiliency as it builds a cache of requests rather than risk dropping one. It also allows for efficiency as it prevents a bottleneck. You would use a load ballancer to increase performance by having an SQS feed into a LB which distributes the requests to multiple different servers completing the function rather than one. Multiple tools achieving slightly different results