Cloud Computing: Declarative vs. Imperative Models for Configuration Management: Which Is Really Better?

March 29, 2015 Off By David
Object Storage

Grazed from ScriptRock.  Author: Editorial Staff.

As a group of concepts, DevOps has converged on several prominent themes including continuous software delivery, automation, and configuration management (CM). These integral pieces often form the pillars of an organization’s DevOps efforts, even as other bigger pieces like overarching best practices and guidelines are still being tried and tested.

Being that DevOps is a relatively new paradigm – movement – methodology – [insert your own label here], standards around it have yet to be codified and set in stone. Organizations are left to identify tools and approaches most suitable for their use cases, and will either swear by or disparage them depending on their level of success…


In terms of CM, it’s a given that one particular methodology may work for a company but not for another. However, seldom do differing approaches generate as much dissent as the declarative and imperative models for CM. The recurring debate over which is superior has garnered staunch supporters on both sides and warrants a closer inspection…

Read more from the source @ http://www.scriptrock.com/blog/articles/declarative-vs.-imperative-models-for-configuration-management