DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
Refcards Trend Reports Events Over 2 million developers have joined DZone. Join Today! Thanks for visiting DZone today,
Edit Profile Manage Email Subscriptions Moderation Admin Console How to Post to DZone Article Submission Guidelines
View Profile
Sign Out
Refcards
Trend Reports
Events
Zones
Culture and Methodologies Agile Career Development Methodologies Team Management
Data Engineering AI/ML Big Data Data Databases IoT
Software Design and Architecture Cloud Architecture Containers Integration Microservices Performance Security
Coding Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
Culture and Methodologies
Agile Career Development Methodologies Team Management
Data Engineering
AI/ML Big Data Data Databases IoT
Software Design and Architecture
Cloud Architecture Containers Integration Microservices Performance Security
Coding
Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance
Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
  1. DZone
  2. Testing, Deployment, and Maintenance
  3. DevOps and CI/CD
  4. Four Steps From Legacy to DevOps

Four Steps From Legacy to DevOps

The first step is to identify legacy code by determining which systems have been running the business since inception.

Yaniv Yehuda user avatar by
Yaniv Yehuda
·
Jun. 03, 16 · Opinion
Like (1)
Save
Tweet
Share
3.28K Views

Join the DZone community and get the full member experience.

Join For Free

in his april 12 piece in the register , michael coté addresses the challenge of transforming ‘legacy’ (pre-devops) software and services into workable infrastructure in the devops era. coté explains how addressing the ‘technical debts’ of dated code segments and systems enables businesses stand to develop “more resilient, more productive” software. here’s coté’s how-to:

the first step is to identify legacy code by determining which systems have been running the business since inception. experimentation with changes at this core level will naturally seem risky, since these models are least subject to testing or critical review. next, making use of portfolio analysis, quarantine lowest-value and virtualize dormant applications. what remains is an isolated set of base applications for devops adaptation . concentrate on these applications, and adapt strategically by means of forklifting, strangling, re-writing, or ignoring:

  1. forklift : adapt directly to a devops-driven, continuous delivery approach; looks the easiest but has the worst long-term payoff
    for legacy applications that are “written to be… self-contained and [independent of] vendor-proprietary services or… network file shares.”
  2. strangle: introduce a new layer of abstraction – an api or set thereof – that fronts the legacy services, eventually replacing capabilities in the legacy system with new code that’s more aligned with your new approach to software development
    for new applications that must use legacy software and services
  3. rewrite : revise dated code for use with devops approach; most time intensive and if done slapdash, risk-laden choice, if done properly achieves frequent change benefits of continuous delivery
    for interdependent legacy applications
  4. ignore : right answer is often to carefully do nothing and instead to focus on your net-new software without letting your legacy software and processes drag you down.
DevOps application Software development

Published at DZone with permission of Yaniv Yehuda, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

Popular on DZone

  • Why You Should Automate Code Reviews
  • How to Quickly Build an Audio Editor With UI
  • PostgreSQL: Bulk Loading Data With Node.js and Sequelize
  • Secrets Management

Comments

Partner Resources

X

ABOUT US

  • About DZone
  • Send feedback
  • Careers
  • Sitemap

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 600 Park Offices Drive
  • Suite 300
  • Durham, NC 27709
  • support@dzone.com
  • +1 (919) 678-0300

Let's be friends: