DevOps is a hot topic. It seems that everyone is talking about it. Some have
built business models around DevOps-related tools and themes. There are
conferences and trade shows dedicated to DevOps-strategies and techniques.
Some people have even made their careers around talking about it. In light of
all of that, I find it chuckle-worthy that very few people actually know what
DevOps is (just follow #devops on Twitter for proof.) I am not going to be
one of many trying to create a buzzword-infested definition of DevOps to suit
my particular agenda. Instead, I'd like to talk about what DevOps is not.
So, without further ado, DevOps ...
...is not a product (or a suite of products)
DevOps is a philosophy. It is an approach, a method. It is not a product. Or
a thing. You can't "buy" DevOps (or its accessories) just to say that you
have it. No matter how many companies are... (more)
Automation is a big part of the DevOps approach, to the point where some
people (incorrectly) define DevOps exclusively as automation. While many
discuss automating the deployment pipeline process for build->test->deploy,
few talk about utility automation for the intermediate steps of that process.
There are different aspects of end-to-end processes that can help improve the
adoption of DevOps principals by developers. There are on-call
responsibilities, development-centric monitoring and process automation for
developers. One of the great techniques for the latter is commit/push ... (more)
I've talked at length about the importance of business process monitoring
alongside of system monitoring, but in discussions I found that sometimes an
overview and simple examples are not enough to convince people about the
benefits of this approach. Business owners think they don't need to know
anything about the operational performance of their systems as long as they
have their numbers, and engineers often don't feel they need to invest time
into understanding the business they are supporting in detail, finding
examples shown too "common sense."
One question we ask our engine... (more)
Content Management Systems (CMS) have become one of the most powerful
Internet-related products. What once was a gadget for web developers and
technology geeks is now a must-have tool for multiple business units. Because
of the pace at which the world of Internet technology changes, and the high
demand for up-to-the-minute content, there are thousands of products
(commercial and open source alike) that offer myriad features to companies in
need of a solution for publishing their content.
Unfortunately, over the past decade, the term "CMS" has become a buzz word, a
commodity if y... (more)
As the holiday rush is winding down, I sit here reflecting on all the
companies that lost business/revenue during the busiest time of the year.
Loss of business not because of technology failure, although this is always a
manifestation of a problem, but because of process failure in order to remedy
the failures of technology. I've offered some tips on preparing for the
holiday traffic from the system architecture perspective, but perhaps I
should have concentrated on preparing for the rush from the organizational
Behind the extensive downtimes I witness every holida... (more)