News

A few weeks ago TechTarget published a great article by Kurt Marko: "To build or to buy? That is the DevOps toolchain question” 
http://searchitoperations.techtarget.com/tip/To-build-or-to-buy-That-is-the-DevOps-toolchain-question

At the end Kurt summarizes an organization's decision to three factors: expertise and comfort toward deploying open source tools, opinionated versus non-opinionated tooling choices, and the underlying PaaS. Allow me to add another important criterion: automation. More to the point, should the automation code play a role in your decision to build or buy?

Until now, development and operations teams have had to choose between a custom-built DevOps pipeline or pre-made toolchain bundled with cloud provider or PaaS offering. A pre-made toolchain is simpler than individually collected tools, but it sacrifices flexibility and control. Organizations that don't want to use an opinionated PaaS stack and pre-defined toolchains, yet don't have the time or expertise to stitch together and manage a myriad of DevOps point products, now have a new option that combines the best of both worlds: full stack automation with machine generated DevOps pipelines.  Agile Stacks can provide customizable DevOps toolchain and create standardized environments, based on machine generated stack automation code.

We are still at an early stage of cloud deployment for the vast majority of companies in the world.  However, surveys show that this is changing rapidly.  The cloud has proven itself in cost, reliability and security.    In fact, the onus has gone the other way now.  

A few months ago Jason Bloomberg published a great article in Forbes:
You're Now 'Cloud First.' Are You Ready To Be 'DevOps First'?

It is so true that in order to unlock the real benefit of the cloud, it's necessary to implement DevOps.   If you don't start with DevOps, "productivity can grind to a halt because development teams can’t deploy their code.”

Cloud and DevOps go hand in hand - while you can have one without another, they are much stronger when applied together.  It's a classic case where the whole is greater than the sum of its parts.

SOA -> API as  PaaS -> Docker 

I frequently make an analogy of why API's have supplanted SOA as being for similar reasons why Docker/Kubernetes is supplanting PaaS.

SOA was architecturally superior and theoretically provided the same benefits as API's.  Many companies went down the SOA road but few ever implemented it very far.  For instance, governance registry is pretty key part of the whole reuse idea in SOA and those were rarely implemented by companies and those that implemented them rarely found much reuse.   Reuse which was a primary goal of SOA and it was never achieved in most companies.