# Load Balancer across stacks
**URL:** https://forums.suse.com/t/load-balancer-across-stacks/345
**Category:** Rancher 1.x
**Created:** [August 27, 2015, 6:46pm UTC](https://forums.suse.com/t/load-balancer-across-stacks/345 "2015-08-27T18:46:47Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@erichorne](https://forums.suse.com/u/erichorne)
#### Post date: [August 27, 2015, 6:46pm UTC](https://forums.suse.com/t/load-balancer-across-stacks/345/1 "2015-08-27T18:46:47Z")
As I understand load balancing within Rancher, stacks may include a load balancer along with services. It is also possible for a load balancer in stack A to balance-load for services in stack B. There are generally, then a few options for load balancing:
1. A load balancer per stack
2. One load balancer for all stacks (e.g. a stack that consists of a load balancer)
What are the benefits of the per-stack load balancer over the single load balancer for all stacks?
Thanks!
-Eric
---
### Author:  [@vincent](https://forums.suse.com/u/vincent)
#### Post date: [August 27, 2015, 10:41pm UTC](https://forums.suse.com/t/load-balancer-across-stacks/345/2 "2015-08-27T22:41:48Z")
It’s pretty much arbitrary since links can cross stacks…
In general you’d want to have all the services that make up a logical product/application/customer (whatever you’re deploying) in one stack, because the service graph, import/export/working with `rancher-compose`, etc are scoped to a stack.
But if for example you’re using layer-7 routing in a loadbalancer to route requests across many applications then it probably doesn’t really belong in any one application, so you might put that in it’s own stack.
---
### Author:  [@kaos](https://forums.suse.com/u/kaos)
#### Post date: [August 28, 2015, 5:36am UTC](https://forums.suse.com/t/load-balancer-across-stacks/345/3 "2015-08-28T05:36:19Z")
I’d also add that you’ll run into issues if you try to run more than one load balancer per host using the same public port… for that reason we use a single load balancer per host for all stacks…