-David Christensen: We chose SaltStack primarily to fix a lot of problems in our environment. We were a window-shop completely deployed inside the cloud and with the scale that we were going to be faced with. We needed something that could actually kind of wrangle at it and Salt was one of the very few orchestration engines out there that could actually handle the windows to the degree that we needed to. - Carson Anderson: I love SaltStack because it's active and reactive it's not a passive way to manage my infrastructure. It's something that I don't have to set something hope that it works and then come back later and find out if it did or not like some of the other tools. It is active. I am in my infrastructure manipulating it in the same kind of way that I'm used to manipulating individual machines except for I'm working at scale, and I think that's really powerful. -Paul Jenson:There's a real learning curve with some of these technologies and the consensus was that using Salt was much more simple easy to get going and reduce that learning curve from sort of getting to implementation to actually using the platform and getting business value. -Jacob Weinstock: The things that hooked me are really how extensible. The Python API was and saw what the product was. And then once I got involved the community hooked me even more. -Senthilkumar Eswaran: We have been one of the early adopters of SaltStack and we have been using SaltStack for the last 7 years. We are at a scale of like 150K nodes that we are using Salt and we use pretty much for all our automation tasks. -Carson Anderson: Salt is the only system automation tool that is this extensive. Extensibility is huge when you get to an enterprise scale and there's nothing else like SaltStack.
