Coffee Talk: Java, News, Stories and Opinions

Oct 19 2016   12:54PM GMT

Understanding the need for continuous deployment

pavanbel Profile: pavanbel

Tags:
Uncategorized

The picture below shows a high-level maturity model for Continuous Deployment. As shown below, there are multiple stages of capability required to achieve Continuous Deployment. It starts with Continuous Integration.

CD Pipeline at shippable

Most organizations today are at L1 or L2 of this maturity model. However, they are constantly looking to improve to higher levels of maturity.

Successful companies such as Facebook, Netflix, and Amazon have achieved L3 and L4 maturity and, as a result, deliver more value through software at a faster pace than traditional software organizations. However, organizations that have achieved this maturity level have often invested a significant amount of time and resources in order to create their Continuous Deployment pipelines. This often occurs with highly customized designs that piece together specific, fragmented tools via thousands of lines of custom code. Once created, these customized pipelines have achieved the desired automation and speed. However, they are often inflexible and difficult to change.

The best approach is to achieve the needed maturity without significant investment or unwanted rigidity. You need a perfect platform that does the work for you, from source control to continuous deployment. This benefits your organization to focus more on the product than doing repeative and time consuming developer work writing lot of code on mundane tasks. If you want to have your own platform this way (that does CI & CD), it’s not possible or may be time consuming and that’s not your product since it involves a lot of cost as said earlier, to spin up servers and other supporting resources, instead you need a platform that helps you mature from L1 to L4 (as shown in the above figure) at your own pace without needing to build homegrown pipelines, and nowadays organizations like Shippable are helping many software-powered organizations to innovate their way to successful software deployment. Whereas most of the tools doesn’t really do CD (Continuous Delivery), in fact, what they do is to end up their work with CI (Continous Integration) but the need is to have a platform that does work from CI to CD & that’s where shippable is approaching.

 Comment on this Post

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when other members comment.

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

Share this item with your network: