# Question about scaling & best practice **URL:** \ **Category:** Rancher 1.x\ **Created:** [June 30, 2016, 12:02pm UTC](https://forums.suse.com/t/question-about-scaling-best-practice/3258 "2016-06-30T12:02:14Z")\ **Posts on this page:** 1\ **Showing post:** 5
**Author:** ![moensch](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/moensch/32/1787_2.png) [@moensch](https://forums.suse.com/u/moensch)\ **Post date:** [June 30, 2016, 6:12pm UTC](https://forums.suse.com/t/question-about-scaling-best-practice/3258/5 "2016-06-30T18:12:45Z")
Being able to scale each service (collection of containers from the same image) independently within a given stack (collection of services) is nice, because you may not always need to have a 1:1 mapping for each of those. As long as you internally use the magic rancher host names as indicated by alexR. However, sometimes you may _need_ to ensure that you have each service within the stack at the same scale. I had some odd requirement for this. The solution is to mark B, C, and D as “side kicks”. My old thread about this is here: > [@Scaling a complete stack (keeping ratios)](http://forums.suse.com/t/scaling-a-complete-stack-keeping-ratios/2426): > > I finally got the time to build out some stacks on Rancher (instead of just playing with dummy stacks) and am very pleased with the result. I am hit with one hurdle though, which is dictated by the software design which I cannot easily change. Background: I have a stack consisting of an event bus (pub/sub) and multiple subscribers. Each event bus must have one, and only one of each type of subscribers. Having two subscribers of the same type on the same event bus would cause data duplication,… --- _[View the full topic](https://forums.suse.com/t/question-about-scaling-best-practice/3258)._