Welcome!

Microservices Expo Authors: Dalibor Siroky, Liz McMillan, John Worthington, Automic Blog, Don MacVittie

Related Topics: FinTech Journal, Microservices Expo, Linux Containers, Containers Expo Blog, @DevOpsSummit

FinTech Journal: Article

Art of Rollback | @DevOpsSummit #API #APM #DevOps #ContinuousTesting

Learn about rollback strategies for static and dynamic objects and how to set your rollback budget

Art of Rollback III: Rollback Strategies Through the Ages
By Pierre-Boris Bonafous

Let's recap what we learned from the previous chapters in the series: episode 1 and episode 2.

We learned that a good rollback mechanism cannot be designed without having an intimate knowledge of the application architecture, the nature of your components and their dependencies. Now that we know what we have to restore and in which order, the question is how?

There are always different possible strategies available to restore your services. The only criteria for deciding which one to choose is speed. For this reason, the rollback must be automated and the best rollback features available must be leveraged for each of your application components and technologies. The automation tool will be in charge of the orchestration of the different technologies involved in the rollback process.

How Much Money Should You Spend on Rollback?
Always go for the fastest process you can afford. No company can afford data loss, data corruption and service interruption. Never cut cost on this part. Trying to reuse old backup systems or mutualized backup, for example, is not advisable, as investing in new technologies can give you more reactivity with an immediate ROI.

The budget of rollback implementation should be calculated at the beginning of your project, according to the cost of an error for the business and not by looking at best solution price or providers' bundles available on the market.

The acceptable cost of an error should not be estimated by Ops or Devs but by the business itself, as it can be a mix of unexpected factors. Some are part of the company plan and should not be shared internally. For example, it can be related to the company share price, risk assessment, compliance and compensation, SLA and penalties, customer retention, sales objectives, transactions per days and so on...

Time is money, so the equation is really easy to solve for Ops: the maximum recovery time objective (RTO) of an application depends on the maximum acceptable loss for the business. Your company may already have defined this metric in the disaster recovery plan.

Unfortunately, like most other technical services, the rollback system is too often taken in account at the end of a project. This is a big mistake as the cost of implementing the rollback can be huge, sometimes higher than essential features like automated deployment or monitoring. The rollback cost does not only include the cost of the implementation and the possible additional tools but also the cost of maintenance and regular testing of the rollback system.

Automic is helping his customers to create value with automation. Automated deployments and automated rollbacks must be considered together as a whole when you want to cover the Release Automation activities.

Static Components
Let's take a look at the most popular rollback strategies implemented today for static components. There are two different ways to manage immutable components: restore and switch.

Restore Rollback: This is the traditional way to roll back, from a time when applications were installed on premise, on physical boxes, and when the materials and software were expensive. Thanks to virtualization, containers and automated provisioning, the restore approach has enjoyed a renaissance. The original intent was to simply to reinstall the previous version of the application(s). That can be done by overriding files, uninstalling/reinstalling binaries or going back to a restoration point.

Today it's more about redelivering the previous complete application stack, pre-configured: the OS, the middleware and the application layer itself. Virtualization has paved the way with templates and Gold VMs. But container technologies like Docker do even better, as you can instantiate a container from an image in a couple of seconds. You have to re-instantiate a container from the previous images instead of delivering old binaries

Automic Release Automation enables you to define rollback at the workflow or job/task level. When the default rollback is activated, you can assign backup and rollback tasks. The backup task will be executed before the main action, while the rollback task will be executed in case of failure.

However, not every application today is a good candidate for containerization. If this is the case, you can go for the switch strategy, to achieve the same outstanding performance but for old systems.

Switch Rollback: Switch rollback maintains two releases of your application in parallel but makes only one accessible to your users while the other remains offline. When you want to deploy a new application release, you install the new release on the offline system. Once the new version is ready you just have to put the old version offline and new version online. If you want to rollback your application, you just switch back.

The switch can be really transparent when the application is a bunch of files in a flat directory. All you have to do is to switch two repositories with the old and the new release content. Sometimes it can be trickier if you rely on an application server or a cluster.

Blue-green deployment is a typical example of switch rollback. The blue environment is offline and the green is online. An environment can be a cluster or collection of machines. The switch (or change of color) can be done quickly by reassigning the IP addresses between the blue and the green machines in the DNS, in the load balancer or at the proxy level. Another advantage of blue-green deployment is that the rollback does not need a specific procedure because it the same procedure used for the initial rollout.

How much does this cost? Well, you must maintain a duplicated platform. That can be quite expensive if your platform is a cluster or a server farm. However, virtualization and automated provisioning can help you to limit the cost of administration, licenses and maintenance of the blue platform if you build and destroy the environments on the fly.

Dynamic Components
As you may be aware, immutable components are not an issue anymore. The problem we must solve today is rolling back dynamic components. Data is now stored on various formats: files, relational databases, NoSQL databases and so on... each technology with its own properties for recovery management.

In this scenario it's difficult to rollback without downtime or data loss if you do not have specific features embedded in the application itself. Some examples of possible function could be a data resilience system, a database virtualization layer, a data cache mechanism or treating your database structure as code.

Let's take an even more simple use case: a database upgrade with zero downtime. Not all databases can support that feature. There is no set plan to follow so you must exploit the best technologies available on the market like checkpoints or point-in-time recovery for databases and snapshots for virtual machines when your software architecture does not support rollback natively.

In fact, the only way to achieve zero downtime and to keep control of your data during deployments and rollbacks is to design backward and forward compatibility in the application itself. But this is another story...

Next Episode
Rolling forward; Why is it better than rollback? Because rolling forward is the best way of accepting that we, Dev and Ops, are intimately involved in time-flow, no matter what Albert Einstein or Brian Green told us! Stay tuned.

More Stories By Automic Blog

Automic, a leader in business automation, helps enterprises drive competitive advantage by automating their IT factory - from on-premise to the Cloud, Big Data and the Internet of Things.

With offices across North America, Europe and Asia-Pacific, Automic powers over 2,600 customers including Bosch, PSA, BT, Carphone Warehouse, Deutsche Post, Societe Generale, TUI and Swisscom. The company is privately held by EQT. More information can be found at www.automic.com.

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 nature of test environments is inherently temporary—you set up an environment, run through an automated test suite, and then tear down the environment. If you can reduce the cycle time for this process down to hours or minutes, then you may be able to cut your test environment budgets considerably. The impact of cloud adoption on test environments is a valuable advancement in both cost savings and agility. The on-demand model takes advantage of public cloud APIs requiring only payment for t...
Agile has finally jumped the technology shark, expanding outside the software world. Enterprises are now increasingly adopting Agile practices across their organizations in order to successfully navigate the disruptive waters that threaten to drown them. In our quest for establishing change as a core competency in our organizations, this business-centric notion of Agile is an essential component of Agile Digital Transformation. In the years since the publication of the Agile Manifesto, the conn...
identify the sources of event storms and performance anomalies will require automated, real-time root-cause analysis. I think Enterprise Management Associates said it well: “The data and metrics collected at instrumentation points across the application ecosystem are essential to performance monitoring and root cause analysis. However, analytics capable of transforming data and metrics into an application-focused report or dashboards are what separates actual application monitoring from relat...
The benefits of automation are well documented; it increases productivity, cuts cost and minimizes errors. It eliminates repetitive manual tasks, freeing us up to be more innovative. By that logic, surely, we should automate everything possible, right? So, is attempting to automate everything a sensible - even feasible - goal? In a word: no. Consider this your short guide as to what to automate and what not to automate.
We just came off of a review of a product that handles both containers and virtual machines in the same interface. Under the covers, implementation of containers defaults to LXC, though recently Docker support was added. When reading online, or searching for information, increasingly we see “Container Management” products listed as competitors to Docker, when in reality things like Rocket, LXC/LXD, and Virtualization are Dockers competitors. After doing some looking around, we have decided tha...
It’s “time to move on from DevOps and continuous delivery.” This was the provocative title of a recent article in ZDNet, in which Kelsey Hightower, staff developer advocate at Google Cloud Platform, suggested that “software shops should have put these concepts into action years ago.” Reading articles like this or listening to talks at most DevOps conferences might make you think that we’re entering a post-DevOps world. But vast numbers of organizations still struggle to start and drive transfo...
Enterprises are adopting Kubernetes to accelerate the development and the delivery of cloud-native applications. However, sharing a Kubernetes cluster between members of the same team can be challenging. And, sharing clusters across multiple teams is even harder. Kubernetes offers several constructs to help implement segmentation and isolation. However, these primitives can be complex to understand and apply. As a result, it’s becoming common for enterprises to end up with several clusters. Thi...
Many enterprise and government IT organizations are realizing the benefits of cloud computing by extending IT delivery and management processes across private and public cloud services. But they are often challenged with balancing the need for centralized cloud governance without stifling user-driven innovation. This strategy requires an approach that fundamentally reshapes how IT is delivered today, shifting the focus from infrastructure to services aggregation, and mixing and matching the bes...
Cavirin Systems has just announced C2, a SaaS offering designed to bring continuous security assessment and remediation to hybrid environments, containers, and data centers. Cavirin C2 is deployed within Amazon Web Services (AWS) and features a flexible licensing model for easy scalability and clear pay-as-you-go pricing. Although native to AWS, it also supports assessment and remediation of virtual or container instances within Microsoft Azure, Google Cloud Platform (GCP), or on-premise. By dr...
"Codigm is based on the cloud and we are here to explore marketing opportunities in America. Our mission is to make an ecosystem of the SW environment that anyone can understand, learn, teach, and develop the SW on the cloud," explained Sung Tae Ryu, CEO of Codigm, in this SYS-CON.tv interview at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
High-velocity engineering teams are applying not only continuous delivery processes, but also lessons in experimentation from established leaders like Amazon, Netflix, and Facebook. These companies have made experimentation a foundation for their release processes, allowing them to try out major feature releases and redesigns within smaller groups before making them broadly available. In his session at 21st Cloud Expo, Brian Lucas, Senior Staff Engineer at Optimizely, discussed how by using ne...
"CA has been doing a lot of things in the area of DevOps. Now we have a complete set of tool sets in order to enable customers to go all the way from planning to development to testing down to release into the operations," explained Aruna Ravichandran, Vice President of Global Marketing and Strategy at CA Technologies, in this SYS-CON.tv interview at DevOps Summit at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
Let's do a visualization exercise. Imagine it's December 31, 2018, and you're ringing in the New Year with your friends and family. You think back on everything that you accomplished in the last year: your company's revenue is through the roof thanks to the success of your product, and you were promoted to Lead Developer. 2019 is poised to be an even bigger year for your company because you have the tools and insight to scale as quickly as demand requires. You're a happy human, and it's not just...
"Opsani helps the enterprise adopt containers, help them move their infrastructure into this modern world of DevOps, accelerate the delivery of new features into production, and really get them going on the container path," explained Ross Schibler, CEO of Opsani, and Peter Nickolov, CTO of Opsani, in this SYS-CON.tv interview at DevOps Summit at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
While some developers care passionately about how data centers and clouds are architected, for most, it is only the end result that matters. To the majority of companies, technology exists to solve a business problem, and only delivers value when it is solving that problem. 2017 brings the mainstream adoption of containers for production workloads. In his session at 21st Cloud Expo, Ben McCormack, VP of Operations at Evernote, discussed how data centers of the future will be managed, how the p...
DevOps teams have more on their plate than ever. As infrastructure needs grow, so does the time required to ensure that everything's running smoothly. This makes automation crucial - especially in the server and network monitoring world. Server monitoring tools can save teams time by automating server management and providing real-time performance updates. As budgets reset for the New Year, there is no better time to implement a new server monitoring tool (or re-evaluate your current solution)....
While we understand Agile as a means to accelerate innovation, manage uncertainty and cope with ambiguity, many are inclined to think that it conflicts with the objectives of traditional engineering projects, such as building a highway, skyscraper or power plant. These are plan-driven and predictive projects that seek to avoid any uncertainty. This type of thinking, however, is short-sighted. Agile approaches are valuable in controlling uncertainty because they constrain the complexity that ste...
"This all sounds great. But it's just not realistic." This is what a group of five senior IT executives told me during a workshop I held not long ago. We were working through an exercise on the organizational characteristics necessary to successfully execute a digital transformation, and the group was doing their ‘readout.' The executives loved everything we discussed and agreed that if such an environment existed, it would make transformation much easier. They just didn't believe it was reali...
"We're developing a software that is based on the cloud environment and we are providing those services to corporations and the general public," explained Seungmin Kim, CEO/CTO of SM Systems Inc., in this SYS-CON.tv interview at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
The cloud revolution in enterprises has very clearly crossed the phase of proof-of-concepts into a truly mainstream adoption. One of most popular enterprise-wide initiatives currently going on are “cloud migration” programs of some kind or another. Finding business value for these programs is not hard to fathom – they include hyperelasticity in infrastructure consumption, subscription based models, and agility derived from rapid speed of deployment of applications. These factors will continue to...