Category Archives: Devops principles
Pushing twice daily: our conversation with Facebook’s Chuck Rossi
At my new job we’re reigniting an effort to move to continuous delivery for our software releases. We figured that we could learn a thing or two from Facebook, so we reached out to Chuck Rossi, Facebook’s first release engineer … Continue reading
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
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
A battle plan for devops in the enterprise
Establishing a devops platform in an enterprise environment is challenging because there are a bunch of groups who own different pieces of the puzzle, and they will generally have different ideas on how to move forward. But there’s a way … Continue reading
The virtues of cowboy development
Sometimes it’s easy to fall into myopic ways of seeing the world. Let’s talk about my favorite recent example, which is the so-called “cowboy developer”. The cowboy developer, the thinking goes, is an organizational problem child because he (or she) … Continue reading
Why you need a devops platform
Until fairly recently, I thought of devops mostly in terms of various sorts of automation: build, test, deployment, operations and SDLC. And while it’s true that automation is key to devops, I think it’s secondary to something even more fundamental. … Continue reading
Devops: what it is and why you should be doing it
Devops is a big deal nowadays, and there’s a variety of ways people describe it and its benefits. Here we’ll move past the fluffy characterization involving developers and operations working together joyously—not to mention the outright wrong characterization of one … Continue reading
Closed loops: the secret to collecting configuration management data
Hi all, Willie here. Happy New Year! In my last post, How NOT to collect configuration management data, I gave a quick rundown of some losing CM data approaches that I and others have attempted in the past. Most of … Continue reading