Puppet has been able to help us implement solutions or guide for possible pitfalls we might run into. There have been bumps and unresolved issues that at times are not directly evident and would require changing the product that might steer away from new incoming users but larger enterprises do not want or require more stringent requirements.

Puppet overall is a good Configuration Management System, I'd say one of the most used systems today. Puppet Enterprise on the other hand has some interesting areas that could use a lot of improvement. The good: * The support provided by PE has been pretty good overall having quick on spot on answers most o the time. * The Puppet Product has lots of usage industry wide and thus it's easy to find already implemented modules out there (Puppet Forge, Stack Overflow, etc.) * Once it's working it won't break most likely The down sides: * There is no good HA solution overall. The best it can be achieved is to have a active/passive model and a somewhat manual process to promote a passive server to active server. This process also is a one way change and the initial server's Application stack needs to be reinstalled. It also doesn't support out of the box any HA DB solution other than a PaaS Cloud Service. * The structure and authentication/authorization mechanisms for the different APIs are difficult to work with. Different APIs endpoint support different authentication/authorization mechanisms thus making automation around p PE processes a pain to handle. * Right now there is no SaaS PE Solution on Azure, thus requiring to deploy several machines to have the proper infrastructure to have a Master of Master server (at least) and Compile Masters to scale horizontally and be able to handle the load.