Love That 'Legacy'
Like it or not, old code is still around, and it needs special care.
Quiz: What is "legacy" software?
a. Cobol/mainframe code
b. Software written before 1990
c. Applications that have become obsolete
d. Poorly documented systems that no one wants to touch
e. Secure, reliable and effective stuff that just keeps running, year after year
Interviews with a number of IT managers turned up all of those definitions, and more.
"Legacy is a word I despise," says Frank da Cruz, an IT manager at Columbia University in New York. "People say 'legacy' and it's like, 'Oh my god, how could you possibly use that old garbage?' But what it really means is that it was written by smart people a long time ago and it really works, instead of being the latest bug-ridden, bloated piece of garbage from some company that has only teenagers working for it."
However you define legacy software, IT people say they know it when they see it, and they know it didn't all go away during Y2k remediation. It's the stuff with poor documentation, spaghetti code stirred by too many cooks, and processing cycles more appropriate for 1970s ways of doing business. And it's definitely not the stuff you tell college recruits about when they come looking for Java, Web services and grid computing.
Frank da Cruz, an IT manager at Columbia University
Image Credit: Manuello Paganelli
But even the most enthusiastic of the legacy loyalists acknowledge that old software often presents special challenges. They employ a number of tricks -- both managerial and technical -- to keep the bits flowing in those old pipes.
Not Older; Better
For Paul Grant, director of retail systems application development at Tower Records in West Sacramento, Calif., "'Legacy' is when the technology can no longer fit the business needs." By that definition, Tower's retail point-of-sale software, some 1 million lines of Cobol code dating to the mid-1980s, isn't legacy software.
Although Tower is modernizing it in various ways - by adding Web services interfaces to other systems, for example -- the underlying Cobol application is likely to serve the company for years to come, Grant says. "A lot of people get caught up in the wow and sexy stuff, but I've been a proponent of keeping what we have rather than starting all over, because I don't see the benefit," he says.
But it would be a mistake to think that Tower Records got
- HTTP Status Code Cheat Sheet Look at the Graph, Find the Code and Boom - You're Solving Problems. Identifying and understanding common HTTP status codes can go a...
- 10 Steps to Application and Network Performance Nirvana 10 simple steps that network operations teams can take to ensure that applications and underlying infrastructure can both be tuned for maximum performance.
- Application Performance Management for Dummies Application performance management helps deliver the application performance users and the business demand. Effectively monitoring and troubleshooting application performance issues requires a comprehensive...
- IDC Report: Optimize IT and Business Gains This IDC Whitepaper outlines how CIOs can understand what the "total cost of data" is across their entire organization and how Delphix can...
- Cloud BI Overview: Jaspersoft for AWS Check out this overview of Jaspersoft for AWS, to easily and affordably build business intelligence solutions as well as embed visualizations and analytics...
- API Management: The Key to Improving the Consumer Travel Experience Join PhoCusWright's Senior Technology Analyst, Norm Rose, as he shares his insights on how travel suppliers and intermediaries can improve industry data flow... All App Development White Papers | Webcasts