Click here to close now.

Welcome!

@MicroservicesE Blog Authors: Lori MacVittie, Cloud Best Practices Network, Liz McMillan, Elizabeth White, Michael Kanasoot

Related Topics: @MicroservicesE Blog, Java IoT, Microsoft Cloud, Linux Containers, @ContainersExpo, SDN Journal

@MicroservicesE Blog: Article

Does Continuous Deployment Mean Continuous Disappointment for Customers?

The “delivery” or “deployment” in continuous delivery doesn’t necessarily imply delivery to the end customer.

By Dhruv Gupta, Director of Product Marketing at Perforce

This article was originally published on the Perforce Blog.

An interesting article came out recently, “Why Continuous Deployment may mean Continuous Disappointment for your Customers.” It correctly identifies the human need for a shiny, new thing every so often. And it argues that the practice of continuous deployment could lead to disenchantment with incremental updates.

The article cites examples of companies whose customers were left disillusioned by incremental additions or subtractions to existing capability.

There are at least a couple of underlying issues to explore.

  • What does it mean to continuously deliver? What are we delivering, to whom, and when?
  • What are my customer’s expectations? Are they being met?

First, it is important to understand that the “delivery” or “deployment” in continuous delivery doesn’t necessarily imply delivery to the end customer. The bible on the subject, “Continuous Delivery” by Jez Humble and David Farley, suggests that continuous delivery simply implies maintaining a state of readiness. The state of readiness implies you did deliver an update to someone. It did go through quality control and stakeholder approvals. However, business gets to decide the what, the whom and the when. This works really well for verticals like cloud-based software, where you might want to deliver new functionality to a select group of customers to begin with, vet that functionality, and then roll out to a larger audience. Continuous delivery doesn’t necessitate delivery of every update to the customer, the moment the code is deployed. In fact, you might deliver daily updates to only your product manager and QA team, and that is it. This distinction is subtle, but often overlooked, leading to confusion.

Second, most business-minded staff would agree that to grow brand appeal it helps to have big announcements at a regular cadence. Depending on the sector, the announcement could be yearly, or quarterly if you just have a primary product line, or at a higher frequency across several product lines. We have seen the likes of Apple announce a new phone, a new device, the one more thing, at least once a year. It builds a sense of mystique and excitement. People wouldn’t wait in lines for a new version of a phone released every month. Building anticipation is essential if you want people to sit up and take notice. In other sectors, a constant stream of updates is more desirable. We see this phenomenon with mobile apps. No big announcements required — just updates. We are used to that. Major updates still come every so often.

This also brings to bear an important issue. Customers don’t like big changes frequently. It takes time for us to get used to a new product. Some products come only at a considerable cost. A new update that arrives sooner than justified by the cost of acquisition can create a backlash. Release a new product too quickly on the heels of the last one—without advance notice—and you might cause angst in the customers who only recently bought the previous version. Loyal customers might feel burnt by the quick update. They might even abandon the brand altogether as a result of feeling the company is apathetic to them. This is especially the case with hardware products—cameras, computers and the like.

If practiced the right way, Continuous Delivery should allow marketers to balance the extremes. You can choose to release incremental updates as they become available to all customers. You can choose to limit major updates or new deliverables until you’re convinced that they satisfy customer requirements, and go for the big launch. Either way, continuous delivery can help return control to the business.

That said, there is much to learn about the impact of Continuous Delivery on a business and its customers. With customers in many different verticals, we have a great vantage point to see how this practice evolves. Our data suggests there’s a lot of movement to this practice. And we’re excited to play an important role in the shift.

To learn more about Continuous Delivery, have a look at our CD Report.

About the Author

dgupta's picture

Dhruv Gupta is the Director of Product Marketing at Perforce Software. See all posts by Dhruv Gupta

Explore Trends in Continuous Delivery at SDLC Acceleration Summit

Want to explore Continuous Delivery trends and best practices along with your peers and industry experts? Join us on May 13 in San Francisco for the SDLC Acceleration Summit.

sdlc_banner_continuous
The summit is designed to help industry leaders address the growing concerns about accelerating software delivery without compromising application quality. This vendor-agnostic summit will explore topics such as:

  • The Future of the SDLC
  • Integrity within the Software Supply Chain
  • Reassessing the True Cost of Software Quality
  • Gaining a Competitive Advantage via an Advanced Software Delivery Process

To kick off this event, Theresa Lanowitz, software industry expert and founder of voke, inc., will be delivering the keynote.

More Stories By Cynthia Dunlop

Cynthia Dunlop, Lead Technical Writer at Parasoft, authors technical articles, documentation, white papers, case studies, and other marketing communications—currently specializing in service virtualization, API testing, DevOps, and continuous testing. She has also co-authored and ghostwritten several books on software development and testing for Wiley and Wiley-IEEE Press. Dunlop holds a BA from UCLA and an MA from Washington State University.

@MicroservicesExpo Stories
Data center models are changing. A variety of technical trends and business demands are forcing that change, most of them centered on the explosive growth of applications. That means, in turn, that the requirements for application delivery are changing. Certainly application delivery needs to be agile, not waterfall. It needs to deliver services in hours, not weeks or months. It needs to be more cost efficient. And more than anything else, it needs to be really, dc infra axisreally, super focus...
Cloud Migration Management (CMM) refers to the best practices for planning and managing migration of IT systems from a legacy platform to a Cloud Provider through a combination professional services consulting and software tools. A Cloud migration project can be a relatively simple exercise, where applications are migrated ‘as is’, to gain benefits such as elastic capacity and utility pricing, but without making any changes to the application architecture, software development methods or busine...
"Plutora provides release and testing environment capabilities to the enterprise," explained Dalibor Siroky, Director and Co-founder of Plutora, in this SYS-CON.tv interview at @DevOpsSummit, held June 9-11, 2015, at the Javits Center in New York City.
Discussions about cloud computing are evolving into discussions about enterprise IT in general. As enterprises increasingly migrate toward their own unique clouds, new issues such as the use of containers and microservices emerge to keep things interesting. In this Power Panel at 16th Cloud Expo, moderated by Conference Chair Roger Strukhoff, panelists addressed the state of cloud computing today, and what enterprise IT professionals need to know about how the latest topics and trends affect t...
Many people recognize DevOps as an enormous benefit – faster application deployment, automated toolchains, support of more granular updates, better cooperation across groups. However, less appreciated is the journey enterprise IT groups need to make to achieve this outcome. The plain fact is that established IT processes reflect a very different set of goals: stability, infrequent change, hands-on administration, and alignment with ITIL. So how does an enterprise IT organization implement change...
Conferences agendas. Event navigation. Specific tasks, like buying a house or getting a car loan. If you've installed an app for any of these things you've installed what's known as a "disposable mobile app" or DMA. Apps designed for a single use-case and with the expectation they'll be "thrown away" like brochures. Deleted until needed again. These apps are necessarily small, agile and highly volatile. Sometimes existing only for a short time - say to support an event like an election, the Wor...
DevOps tends to focus on the relationship between Dev and Ops, putting an emphasis on the ops and application infrastructure. But that’s changing with microservices architectures. In her session at DevOps Summit, Lori MacVittie, Evangelist for F5 Networks, will focus on how microservices are changing the underlying architectures needed to scale, secure and deliver applications based on highly distributed (micro) services and why that means an expansion into “the network” for DevOps.
Containers have changed the mind of IT in DevOps. They enable developers to work with dev, test, stage and production environments identically. Containers provide the right abstraction for microservices and many cloud platforms have integrated them into deployment pipelines. DevOps and Containers together help companies to achieve their business goals faster and more effectively. In his session at DevOps Summit, Ruslan Synytsky, CEO and Co-founder of Jelastic, reviewed the current landscape of...
The cloud has transformed how we think about software quality. Instead of preventing failures, we must focus on automatic recovery from failure. In other words, resilience trumps traditional quality measures. Continuous delivery models further squeeze traditional notions of quality. Remember the venerable project management Iron Triangle? Among time, scope, and cost, you can only fix two or quality will suffer. Only in today's DevOps world, continuous testing, integration, and deployment upend...
Sharding has become a popular means of achieving scalability in application architectures in which read/write data separation is not only possible, but desirable to achieve new heights of concurrency. The premise is that by splitting up read and write duties, it is possible to get better overall performance at the cost of a slight delay in consistency. That is, it takes a bit of time to replicate changes initiated by a "write" to the read-only master database. It's eventually consistent, and it'...
While DevOps most critically and famously fosters collaboration, communication, and integration through cultural change, culture is more of an output than an input. In order to actively drive cultural evolution, organizations must make substantial organizational and process changes, and adopt new technologies, to encourage a DevOps culture. Moderated by Andi Mann, panelists discussed how to balance these three pillars of DevOps, where to focus attention (and resources), where organizations migh...
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.
Mashape is bringing real-time analytics to microservices with the release of Mashape Analytics. First built internally to analyze the performance of more than 13,000 APIs served by the mashape.com marketplace, this new tool provides developers with robust visibility into their APIs and how they function within microservices. A purpose-built, open analytics platform designed specifically for APIs and microservices architectures, Mashape Analytics also lets developers and DevOps teams understand w...
Buzzword alert: Microservices and IoT at a DevOps conference? What could possibly go wrong? In this Power Panel at DevOps Summit, moderated by Jason Bloomberg, the leading expert on architecting agility for the enterprise and president of Intellyx, panelists peeled away the buzz and discuss the important architectural principles behind implementing IoT solutions for the enterprise. As remote IoT devices and sensors become increasingly intelligent, they become part of our distributed cloud envir...
Sumo Logic has announced comprehensive analytics capabilities for organizations embracing DevOps practices, microservices architectures and containers to build applications. As application architectures evolve toward microservices, containers continue to gain traction for providing the ideal environment to build, deploy and operate these applications across distributed systems. The volume and complexity of data generated by these environments make monitoring and troubleshooting an enormous chall...
Containers and Docker are all the rage these days. In fact, containers — with Docker as the leading container implementation — have changed how we deploy systems, especially those comprised of microservices. Despite all the buzz, however, Docker and other containers are still relatively new and not yet mainstream. That being said, even early Docker adopters need a good monitoring tool, so last month we added Docker monitoring to SPM. We built it on top of spm-agent – the extensible framework f...
There's a lot of things we do to improve the performance of web and mobile applications. We use caching. We use compression. We offload security (SSL and TLS) to a proxy with greater compute capacity. We apply image optimization and minification to content. We do all that because performance is king. Failure to perform can be, for many businesses, equivalent to an outage with increased abandonment rates and angry customers taking to the Internet to express their extreme displeasure.
There's a lot of things we do to improve the performance of web and mobile applications. We use caching. We use compression. We offload security (SSL and TLS) to a proxy with greater compute capacity. We apply image optimization and minification to content. We do all that because performance is king. Failure to perform can be, for many businesses, equivalent to an outage with increased abandonment rates and angry customers taking to the Internet to express their extreme displeasure.
SYS-CON Events announced today that the "Second Containers & Microservices Conference" will take place November 3-5, 2015, at the Santa Clara Convention Center, Santa Clara, CA, and the “Third Containers & Microservices Conference” will take place June 7-9, 2016, at Javits Center in New York City. Containers and microservices have become topics of intense interest throughout the cloud developer and enterprise IT communities.
The causality question behind Conway’s Law is less about how changing software organizations can lead to better software, but rather how companies can best leverage changing technology in order to transform their organizations. Hints at how to answer this question surprisingly come from the world of devops – surprising because the focus of devops is ostensibly on building and deploying better software more quickly. Be that as it may, there’s no question that technology change is a primary fac...