Tag Archives: architecture

Designing configuration management schemas

One important issue that comes up when undertaking a configuration management effort is how to design “the schema” for configuration management data. Obviously there’s no one-size-fits-all answer here. But there are a couple of general and complementary approaches you need … Continue reading

Posted in Architecture, Configuration management, Devops principles | Tagged , , , | 1 Comment

Large-scale continuous integration requires code modularity

Where large development teams and codebases are involved, code modularity is a key enabler for continuous delivery. At a high level this shouldn’t be too terribly surprising—it’s easier to move a larger number of smaller pieces through the deployment pipeline … Continue reading

Posted in Architecture, Continuous integration, Devops principles | Tagged , , | Leave a comment

When building a CMDB, separate the UI from the API

One lesson I’ve learned in building CMDBs is to cleanly separate the UI from the web service API. In the Java world, for example, this means that the API should be its own package (e.g., WAR file). The UI should … Continue reading

Posted in Architecture, Devops principles | Tagged , , , , , , , | Leave a comment

Architecture and Conway’s law

“…organizations which design systems … are constrained to produce designs which are copies of the communication structures of these organizations.” —Melvin Conway Conway’s law is a well-known fact of life in technology organizations. Eric S. Raymond noted that “[i]f you … Continue reading

Posted in Architecture, Organizational | Tagged , , , | Leave a comment