Click here to close now.


Microservices Expo Authors: Yeshim Deniz, Pat Romanski, Liz McMillan, Elizabeth White, Lori MacVittie

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
The APN DevOps Competency highlights APN Partners who demonstrate deep capabilities delivering continuous integration, continuous delivery, and configuration management. They help customers transform their business to be more efficient and agile by leveraging the AWS platform and DevOps principles.
Containers are changing the security landscape for software development and deployment. As with any security solutions, security approaches that work for developers, operations personnel and security professionals is a requirement. In his session at @DevOpsSummit, Kevin Gilpin, CTO and Co-Founder of Conjur, will discuss various security considerations for container-based infrastructure and related DevOps workflows.
Containers are revolutionizing the way we deploy and maintain our infrastructures, but monitoring and troubleshooting in a containerized environment can still be painful and impractical. Understanding even basic resource usage is difficult - let alone tracking network connections or malicious activity. In his session at DevOps Summit, Gianluca Borello, Sr. Software Engineer at Sysdig, will cover the current state of the art for container monitoring and visibility, including pros / cons and li...
Between the compelling mockups and specs produced by analysts, and resulting applications built by developers, there exists a gulf where projects fail, costs spiral, and applications disappoint. Methodologies like Agile attempt to address this with intensified communication, with partial success but many limitations. In his session at DevOps Summit, Charles Kendrick, CTO and Chief Architect at Isomorphic Software, will present a revolutionary model enabled by new technologies. Learn how busine...
IT data is typically silo'd by the various tools in place. Unifying all the log, metric and event data in one analytics platform stops finger pointing and provides the end-to-end correlation. Logs, metrics and custom event data can be joined to tell the holistic story of your software and operations. For example, users can correlate code deploys to system performance to application error codes.
With containerization using Docker, the orchestration of containers using Kubernetes, the self-service model for provisioning your projects and applications and the workflows we built in OpenShift is the best in class Platform as a Service that enables introducing DevOps into your organization with ease. In his session at DevOps Summit, Veer Muchandi, PaaS evangelist with RedHat, will provide a deep dive overview of OpenShift v3 and demonstrate how it helps with DevOps.
Manufacturing has widely adopted standardized and automated processes to create designs, build them, and maintain them through their life cycle. However, many modern manufacturing systems go beyond mechanized workflows to introduce empowered workers, flexible collaboration, and rapid iteration. Such behaviors also characterize open source software development and are at the heart of DevOps culture, processes, and tooling.
The web app is agile. The REST API is agile. The testing and planning are agile. But alas, data infrastructures certainly are not. Once an application matures, changing the shape or indexing scheme of data often forces at best a top down planning exercise and at worst includes schema changes that force downtime. The time has come for a new approach that fundamentally advances the agility of distributed data infrastructures. Come learn about a new solution to the problems faced by software organ...
Any Ops team trying to support a company in today’s cloud-connected world knows that a new way of thinking is required – one just as dramatic than the shift from Ops to DevOps. The diversity of modern operations requires teams to focus their impact on breadth vs. depth. In his session at DevOps Summit, Adam Serediuk, Director of Operations at xMatters, Inc., will discuss the strategic requirements of evolving from Ops to DevOps, and why modern Operations has begun leveraging the “NoOps” approa...
Internet of Things (IoT) will be a hybrid ecosystem of diverse devices and sensors collaborating with operational and enterprise systems to create the next big application. In their session at @ThingsExpo, Bramh Gupta, founder and CEO of, and Fred Yatzeck, principal architect leading product development at, discussed how choosing the right middleware and integration strategy from the get-go will enable IoT solution developers to adapt and grow with the industry, while at th...
The last decade was about virtual machines, but the next one is about containers. Containers enable a service to run on any host at any time. Traditional tools are starting to show cracks because they were not designed for this level of application portability. Now is the time to look at new ways to deploy and manage applications at scale. In his session at @DevOpsSummit, Brian “Redbeard” Harrington, a principal architect at CoreOS, will examine how CoreOS helps teams run in production. Attende...
In their session at DevOps Summit, Asaf Yigal, co-founder and the VP of Product at, and Tomer Levy, co-founder and CEO of, will explore the entire process that they have undergone – through research, benchmarking, implementation, optimization, and customer success – in developing a processing engine that can handle petabytes of data. They will also discuss the requirements of such an engine in terms of scalability, resilience, security, and availability along with how the archi...
“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.
DevOps has often been described in terms of CAMS: Culture, Automation, Measuring, Sharing. While we’ve seen a lot of focus on the “A” and even on the “M”, there are very few examples of why the “C" is equally important in the DevOps equation. In her session at @DevOps Summit, Lori MacVittie, of F5 Networks, will explore HTTP/1 and HTTP/2 along with Microservices to illustrate why a collaborative culture between Dev, Ops, and the Network is critical to ensuring success.
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.
Saviynt Inc. has announced the availability of the next release of Saviynt for AWS. The comprehensive security and compliance solution provides a Command-and-Control center to gain visibility into risks in AWS, enforce real-time protection of critical workloads as well as data and automate access life-cycle governance. The solution enables AWS customers to meet their compliance mandates such as ITAR, SOX, PCI, etc. by including an extensive risk and controls library to detect known threats and b...
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...
Overgrown applications have given way to modular applications, driven by the need to break larger problems into smaller problems. Similarly large monolithic development processes have been forced to be broken into smaller agile development cycles. Looking at trends in software development, microservices architectures meet the same demands. Additional benefits of microservices architectures are compartmentalization and a limited impact of service failure versus a complete software malfunction....
At DevOps Summit NY there’s been a whole lot of talk about not just DevOps, but containers, IoT, and microservices. Sessions focused not just on the cultural shift needed to grow at scale with a DevOps approach, but also made sure to include the network ”plumbing” needed to ensure success as applications decompose into the microservice architectures enabling rapid growth and support for the Internet of (Every)Things.
For it to be SOA – let alone SOA done right – we need to pin down just what "SOA done wrong" might be. First-generation SOA with Web Services and ESBs, perhaps? But then there's second-generation, REST-based SOA. More lightweight and cloud-friendly, but many REST-based SOA practices predate the microservices wave. Today, microservices and containers go hand in hand – only the details of "container-oriented architecture" are largely on the drawing board – and are not likely to look much like S...