Welcome!

Microservices Expo Authors: Dalibor Siroky, Elizabeth White, Pat Romanski, John Katrick, Liz McMillan

Related Topics: @DevOpsSummit, Microservices Expo, Containers Expo Blog

@DevOpsSummit: Blog Feed Post

Continuous Delivery and Legacy Software | @DevOpsSummit #DevOps #Microservices

Don't Leave Legacy Software Systems Out of the Equation

The future of software releases is clear. Continuous delivery is here to stay. But does that mean that legacy software systems and infrastructure need to be altogether abandoned?

If you polled the people busy redefining best practices today, they'd agree that in a decade we're going to be effortlessly collaborating on highly complex systems that are updated continuously. QA will be fully automated, deployment and infrastructure tasks will be immediate, and large enterprise-wide software projects will be able to move quickly.

In the future, software releases won't feel so "manual." We won't be sitting on 50-person conference calls talking about release-related downtime and asking teams to stay up all night to deliver software. As the software industry continues to mature, creating tools designed to facilitate rapid software delivery, we'll get there, but it's going to take some time.

For Some: The Future is Now

We can see this reality already in a few widely publicized, exception cases. Companies like Flickr and Etsy laid the foundations for rapid, continuous delivery of software to production, and as larger businesses start to adopt DevOps practices we're a few years into an industry-wide rush toward more agile approaches to release management.

Teams at Twitter and Facebook are pushing to production every single day (and often more frequently than that), but the common attribute for many of the companies moving faster is that they don't have to support the legacy software systems present throughout most established businesses. While everyone agrees that continuous delivery is the goal, it remains to be seen how many organizations are going to migrate not just their newer, greenfield projects, but how they are going to accelerate existing, legacy systems.

Don't Leave Legacy Software Systems Out of the Equation

Small and medium-sized businesses in technology and media industries lead the way toward agile software delivery because they don't have to deal with the technologies you might find at a multi-national bank or a global insurance company. Legacy applications carry with them legacy databases built on technologies thatdon't lend themselves to instant deployment models, but there are tools and technologies designed to bridge these gaps.

If you run a large, revenue-generating application there's a good chance that you deal with massive databases from IBM or Oracle. It's even more likely if your system supports business at scale that your application depends on several levels of middleware and multiple databases spanning a whole range of vendors and technologies. Until you can bring these systems along for the daily release schedule there's still work to be done.

Databases Can be Agile Too

I'm picking on databases because they are always the toughest aspect of enterprise release management, and they often present the most difficult challenges to moving toward fast-paced release cadences.

When your release timelines become constrained it's always the databases that complicate everything. In a complex release you need to account for set up and tear down time when planning your testing environment's database requirements. In a production-facing software release it is always the database operations that present the most risk in the process. Databases need to be migrated in one-off processes with little room for error, and during some releases database changes almost invariably call for production downtime.

The good news is that database vendors and other companies supporting tools such as Oracle and DB2 are developing novel solutions to make databases more agile. Test environments can now use data that is continuously masked from production data, and vendors are innovating with various approaches to block storage to make it easier to track database changes and perform rollbacks instantly.

Conclusion: Don't discount legacy databases when it comes to continuous delivery. All signs are pointing toward a future that incorporates more agile data management practices that will facilitate continuous delivery models.

Follow Old Advice: Divide and Conquer

Anyone in charge of an IT budget understands that you have to choose your battles wisely. If we wanted to upgrade every system in the department at once it would be easier if we also had an infinite budget and the ability to hire resources at the snap of a finger. Needless to say, this isn't how most organizations work. In reality, our resources are constrained, and, forget about the budget, the limited resource is often people. It's tough to hire good enterprise release managers, and once you hire a good ERM it takes months (or years) for them to get enough experience to truly manage across your enterprise.

You are not going to move your entire enterprise to a continuous delivery cadence in a year. You are going to move your enterprise to a more continuous delivery cadence over a number of years, and you should create a multi-year plan to do this in phases. In the first stage select the most difficult component (often your relational databases) along with the easiest component (one of your newer web applications.) Focus your efforts on creating a model for other teams to follow once you've successfully moved to a continuous release cadence, and use these initial projects as a chance to experiment with what works and what doesn't.

Conclusion: Don't try to move everything to continuous delivery at once. Choose your battles and understand how to support mixed release models (with Plutora.)

Don't Fight Uphill: Better Yet, Don't Fight at All

When you are acting as a change-agent in the enterprise it will be tempting to talk about continuous delivery as a "revolution." This is an easy trap to fall in because technology is in an almost constant state of reinvention. At almost every large company the pattern is the same: every few years the "old" platform is being replaced by a "new" platform. In the process of selling a rewrite the organization may have brought in new management or gone through a reorg in an effort to get it right.

The secret of almost every large IT organization is that the people maintaining those legacy databases, they occupy the "high ground," and they've seen your rewrite before. The technical experts in charge of your company's critical Oracle databases have heard the arguments for moving faster several times over several years, and they are more than willing to help... but not if you keep on talking about them as being "old and antiquated."

Don't frame your movement toward continuous delivery as a "revolution" aimed at "fixing bad, legacy practices." In fact, don't use the word "legacy" at all. When you use that term you immediately tell the bulk of your IT department that what they are working on is worthless, and you'll be fighting an uphill battle against people determined to prove you wrong.

Conclusion: Don't use battle metaphors. Don't fight. Enlist the help of your existing staff and engage them in an effort to improve an existing system to make it more amenable to continuous delivery.

Future: The Right Tools, The Right Approach

This future of rapid software delivery supported by pervasive automation is a goal we'll achieve in the next decade, but getting there is going to require a lot of organization and planning. To support your transition to continuous delivery, you should use a tool like Plutora to manage projects as you move to continuous delivery while taking your legacy software systems along for the ride.

Read the original blog entry...

More Stories By Plutora Blog

Plutora provides Enterprise Release and Test Environment Management SaaS solutions aligning process, technology, and information to solve release orchestration challenges for the enterprise.

Plutora’s SaaS solution enables organizations to model release management and test environment management activities as a bridge between agile project teams and an enterprise’s ITSM initiatives. Using Plutora, you can orchestrate parallel releases from several independent DevOps groups all while giving your executives as well as change management specialists insight into overall risk.

Supporting the largest releases for the largest organizations throughout North America, EMEA, and Asia Pacific, Plutora provides proof that large companies can adopt DevOps while managing the risks that come with wider adoption of self-service and agile software development in the enterprise. Aligning process, technology, and information to solve increasingly complex release orchestration challenges, this Gartner “Cool Vendor in IT DevOps” upgrades the enterprise release management from spreadsheets, meetings, and email to an integrated dashboard giving release managers insight and control over large software releases.

@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...
"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...
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...
"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.
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...
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...
"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...
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...
"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.
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...
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...
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...
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...
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...
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)....
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...
"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.
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.
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...