Category 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
A fatal impedance mismatch for continuous delivery
Most of the time, when organizations pursue a continuous delivery capability, they’re doing that in pursuit of increased agility. They want to be able to release software at will, with as little delay between the decision to implement a feature … Continue reading
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
Continuous integration with GitHub, Bamboo and Nexus
This is the first in what will be a series of posts on how to establish a continuous delivery pipeline. The eventual goal is to have an app that we can push out into production anytime we like, safely and … Continue reading
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
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