3 ms·
Containers are the way to go if your application can be containerized. It's much easier to configure and deploy the application and its environment this way. It
by nunez 7y ago
Containers are the way to go if your application can be containerized. It's much easier to configure and deploy the application and its environment this way. It's also much easier to test a production-like copy of the application in development without having to spin up a bunch of infrastructure locally.
Assuming that you can't or aren't able to containerize your app, Ansible is a great all-arounder largely because of it being agentless. It's easy to install and easy to scale. However, really large organizations usually want to use their configuration management as a CMDB of sorts. While Red Hat has Ansible Tower for this, Chef provides a much more mature offering (from hearsay; I haven't actually used Tower).
I dismiss Puppet these days. It's more legacy compared to Chef, and it's harder to get recent information when searching for stuff. It's also really hard to test locally compared to Chef with test-kitchen.
- freedomben 7y agoI largely agree. Containerize as much as possible, then use Chef or Ansible for the rest. If you know and use Ruby, Chef can be a good choice. Otherwise, go with Ansible. It's a lot more simple and flexible IMHO, and it's growing rapidly (for those reasons). A note tho, while Chef is Ruby it is still a DSL that will take some time to learn, which puts it on the same level as Ansible's YAML based "language" that you have to learn. I like Chef but despite being a Ruby fanboi I still use Ansible for all new development. It's just a better developer experience.