Click here to close now.


Microservices Expo Authors: Jason Bloomberg, Pat Romanski, AppDynamics Blog, Liz McMillan, XebiaLabs Blog

Related Topics: Microsoft Cloud, Java IoT, Microservices Expo, IoT User Interface, Silverlight, Agile Computing

Microsoft Cloud: Article

Step Away from One-off Release Thinking

The Continuous Delivery Approach

Not long ago, customers and prospects had to find a computer to visit your website. But today they're online 24/7 via mobile devices. Serving your customers is now a continuous interaction, and this phenomenon will only grow in the coming years as customers and prospects demand reliable and up-to-date Web services from anywhere at any time. For your organization, this translates into constant pressure to quickly and frequently add features and updates to your application services.

The environment also makes the quality of your online services more important than ever as issues become visible instantly. Applications to support your business need to be deployed not only at a much faster rate, but also with more predictability. For many organizations, a new approach to delivering software isn't simply about development and deployment practices - it's critical to business survival.

But for most organizations, software delivery is time-consuming, stressful and costly.

As soon as applications go live, issues arise - forcing IT into another costly release cycle. Businesses thus need a process that enables the addition of new online features in a matter of hours instead of days - faster, better and at a lower cost.

The Continuous Delivery Approach
One way that many businesses overcome the challenge of promptly delivering software updates is to adopt the Continuous Delivery approach - a strategy that moves ideas into production as fast and as efficiently as possible. This iterative approach also allows you to validate business assumptions at an early stage of the delivery process and adjust when required.

With Continuous Delivery, your ideas reach customers much faster compared to non-automated, "big bang" release environments. Because the focus is on automating your pipeline, delivery becomes more reliable. A well-designed automated software delivery pipeline typically features the following attributes:

  1. Manages code in version control
  2. Performs compilation and packaging of code centrally and automatically
  3. Automates testing as part of the delivery process
  4. Deploys applications automatically to multiple environments
  5. Creates and removes server environments with the push of a button
  6. Provides clear, factual and quality-focused status reports

Benefits of Continuous Delivery
Continuous Delivery lowers costs since deployments run reliably on a daily basis, and the number of deployments does not significantly impact the overall cost. Once a deployment pipeline is configured, subsequent deployments occur automatically so the maximum number of deployments is not bound to any limit.

With the Continuous Delivery approach, your organization can also envision an idea and then design and realize the benefits in stages. In addition, the process provides the possibility to adjust the scope and requirements as well as support the decision to stop investing in features that don't provide value.

Because customer behavior can be measured as the product evolves, the product also aligns better with demand compared to traditional situations. In addition, the process of assembling, compiling and testing also becomes automated. This forms an integral part of the delivery process that is quick and easy. Coding issues become immediately visible and can be fixed promptly.

Creating a Continuous Delivery Process
To adopt a Continuous Delivery process, first take an assessment to gain a clear picture of the current status of your delivery processes. Assessment is essential to determine the order, approach and expected timelines. Then streamline the process by adopting these best practices:

  • Engage the development team to discuss the approach and how to implement a fresh and automated delivery process. Encourage the team to participate in determining requirements for the new environment, especially where the current process can be optimized.
  • Implement and align tools and processes to consolidate configuration management systems; align the build and automated test tools; introduce the definitive software library; and add application release automation mechanisms. Explain and document concepts and guidelines to ensure proper use for subsequent teams that utilize the new approach.
  • Formalize the environment once the new tools and principles are in place and then introduce other development initiatives. Also make sure short and descriptive explanations of the new process are available to guide people in applying them. Slowly step away from release-like thinking toward incrementally bringing new functionality into production.

The Payoff: Ensuring Prompt and Accurate Communications
Trying to serve today's always-connected, always-updated customers and prospects with anything less than a fully automated application delivery process makes no sense. Software delivery needs to evolve from an effort-intensive, error-prone "big bang" activity to a seamless, incremental and Continuous Delivery process that is faster and more efficient.

For the Continuous Delivery software approach to succeed, everybody has to share a product-like mindset and feel responsible for the end result - from business leaders all the way to operations. Within the development team, if anyone breaks the build - meaning they leave the code broken - they must fix the build before going home. Code in the pipeline has to be shippable at all times.

Continuous Delivery is achieved when all involved are capable of delivering new functionality in an agile manner. Your business will ensure prompt and accurate communications with customers and prospects at all times.

More Stories By Andrew Phillips

Andrew Phillips heads up product management at XebiaLabs. He is an evangelist and thought leader in the DevOps, Cloud and Continuous Delivery space. He sits on the management team and drives product direction, positioning and planning.

Comments (0)

Share your thoughts on this story.

Add your comment
You must be signed in to add a comment. Sign-in | Register

In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.

@MicroservicesExpo Stories
Somebody call the buzzword police: we have a serious case of microservices-washing in progress. The term “microservices-washing” is derived from “whitewashing,” meaning to hide some inconvenient truth with bluster and nonsense. We saw plenty of cloudwashing a few years ago, as vendors and enterprises alike pretended what they were doing was cloud, even though it wasn’t. Today, the hype around microservices has led to the same kind of obfuscation, as vendors and enterprise technologists alike ar...
SYS-CON Events announced today that G2G3 will exhibit at SYS-CON's @DevOpsSummit Silicon Valley, which will take place on November 3–5, 2015, at the Santa Clara Convention Center in Santa Clara, CA. Based on a collective appreciation for user experience, design, and technology, G2G3 is uniquely qualified and motivated to redefine how organizations and people engage in an increasingly digital world.
If you are new to Python, you might be confused about the different versions that are available. Although Python 3 is the latest generation of the language, many programmers still use Python 2.7, the final update to Python 2, which was released in 2010. There is currently no clear-cut answer to the question of which version of Python you should use; the decision depends on what you want to achieve. While Python 3 is clearly the future of the language, some programmers choose to remain with Py...
“All our customers are looking at the cloud ecosystem as an important part of their overall product strategy. Some see it evolve as a multi-cloud / hybrid cloud strategy, while others are embracing all forms of cloud offerings like PaaS, IaaS and SaaS in their solutions,” noted Suhas Joshi, Vice President – Technology, at Harbinger Group, in this exclusive Q&A with Cloud Expo Conference Chair Roger Strukhoff.
Opinions on how best to package and deliver applications are legion and, like many other aspects of the software world, are subject to recurring trend cycles. On the server-side, the current favorite is container delivery: a “full stack” approach in which your application and everything it needs to run are specified in a container definition. That definition is then “compiled” down to a container image and deployed by retrieving the image and passing it to a container runtime to create a running...
Clearly the way forward is to move to cloud be it bare metal, VMs or containers. One aspect of the current public clouds that is slowing this cloud migration is cloud lock-in. Every cloud vendor is trying to make it very difficult to move out once a customer has chosen their cloud. In his session at 17th Cloud Expo, Naveen Nimmu, CEO of Clouber, Inc., will advocate that making the inter-cloud migration as simple as changing airlines would help the entire industry to quickly adopt the cloud wit...
As the world moves towards more DevOps and microservices, application deployment to the cloud ought to become a lot simpler. The microservices architecture, which is the basis of many new age distributed systems such as OpenStack, NetFlix and so on, is at the heart of Cloud Foundry - a complete developer-oriented Platform as a Service (PaaS) that is IaaS agnostic and supports vCloud, OpenStack and AWS. In his session at 17th Cloud Expo, Raghavan "Rags" Srinivas, an Architect/Developer Evangeli...
Culture is the most important ingredient of DevOps. The challenge for most organizations is defining and communicating a vision of beneficial DevOps culture for their organizations, and then facilitating the changes needed to achieve that. Often this comes down to an ability to provide true leadership. As a CIO, are your direct reports IT managers or are they IT leaders? The hard truth is that many IT managers have risen through the ranks based on their technical skills, not their leadership ab...
Apps and devices shouldn't stop working when there's limited or no network connectivity. Learn how to bring data stored in a cloud database to the edge of the network (and back again) whenever an Internet connection is available. In his session at 17th Cloud Expo, Bradley Holt, Developer Advocate at IBM Cloud Data Services, will demonstrate techniques for replicating cloud databases with devices in order to build offline-first mobile or Internet of Things (IoT) apps that can provide a better, ...
Despite all the talk about public cloud services and DevOps, you would think the move to cloud for enterprises is clear and simple. But in a survey of almost 1,600 IT decision makers across the USA and Europe, the state of the cloud in enterprise today is still fraught with considerable frustration. The business case for apps in the real world cloud is hybrid, bimodal, multi-platform, and difficult. Download this report commissioned by NTT Communications to see the insightful findings – registra...
Application availability is not just the measure of “being up”. Many apps can claim that status. Technically they are running and responding to requests, but at a rate which users would certainly interpret as being down. That’s because excessive load times can (and will be) interpreted as “not available.” That’s why it’s important to view ensuring application availability as requiring attention to all its composite parts: scalability, performance, and security.
SYS-CON Events announced today that HPM Networks will exhibit at the 17th International Cloud Expo®, which will take place on November 3–5, 2015, at the Santa Clara Convention Center in Santa Clara, CA. For 20 years, HPM Networks has been integrating technology solutions that solve complex business challenges. HPM Networks has designed solutions for both SMB and enterprise customers throughout the San Francisco Bay Area.
There once was a time when testers operated on their own, in isolation. They’d huddle as a group around the harsh glow of dozens of CRT monitors, clicking through GUIs and recording results. Anxiously, they’d wait for the developers in the other room to fix the bugs they found, yet they’d frequently leave the office disappointed as issues were filed away as non-critical. These teams would rarely interact, save for those scarce moments when a coder would wander in needing to reproduce a particula...
All we need to do is have our teams self-organize, and behold! Emergent design and/or architecture springs up out of the nothingness! If only it were that easy, right? I follow in the footsteps of so many people who have long wondered at the meanings of such simple words, as though they were dogma from on high. Emerge? Self-organizing? Profound, to be sure. But what do we really make of this sentence?
As we increasingly rely on technology to improve the quality and efficiency of our personal and professional lives, software has become the key business differentiator. Organizations must release software faster, as well as ensure the safety, security, and reliability of their applications. The option to make trade-offs between time and quality no longer exists—software teams must deliver quality and speed. To meet these expectations, businesses have shifted from more traditional approaches of d...
Information overload has infiltrated our lives. From the amount of news available and at our fingertips 24/7, to the endless choices we have when making a simple purchase, to the quantity of emails we receive on a given day, it’s increasingly difficult to sift out the details that really matter. When you envision your cloud monitoring system, the same thinking applies. We receive a lot of useless data that gets fed into the system, and the reality is no one in IT or DevOps has the time to manu...
Last month, my partners in crime – Carmen DeArdo from Nationwide, Lee Reid, my colleague from IBM and I wrote a 3-part series of blog posts on We titled our posts the Simple Math, Calculus and Art of DevOps. I would venture to say these are must-reads for any organization adopting DevOps. We examined all three ascpects – the Cultural, Automation and Process improvement side of DevOps. One of the key underlying themes of the three posts was the need for Cultural change – things like t...
It is with great pleasure that I am able to announce that Jesse Proudman, Blue Box CTO, has been appointed to the position of IBM Distinguished Engineer. Jesse is the first employee at Blue Box to receive this honor, and I’m quite confident there will be more to follow given the amazing talent at Blue Box with whom I have had the pleasure to collaborate. I’d like to provide an overview of what it means to become an IBM Distinguished Engineer.
I’ve been thinking a bit about microservices (μServices) recently. My immediate reaction is to think: “Isn’t this just yet another new term for the same stuff, Web Services->SOA->APIs->Microservices?” Followed shortly by the thought, “well yes it is, but there are some important differences/distinguishing factors.” Microservices is an evolutionary paradigm born out of the need for simplicity (i.e., get away from the ESB) and alignment with agile (think DevOps) and scalable (think Containerizati...
The cloud has reached mainstream IT. Those 18.7 million data centers out there (server closets to corporate data centers to colocation deployments) are moving to the cloud. In his session at 17th Cloud Expo, Achim Weiss, CEO & co-founder of ProfitBricks, will share how two companies – one in the U.S. and one in Germany – are achieving their goals with cloud infrastructure. More than a case study, he will share the details of how they prioritized their cloud computing infrastructure deployments ...