Book Image

Working with Legacy Systems

By : Robert Annett
Book Image

Working with Legacy Systems

By: Robert Annett

Overview of this book

The IT industry is constantly evolving with the introduction of new technologies. While it is important to keep up with advancements, maintaining legacy systems is equally necessary to ensure that the infrastructure of your organization functions to the best of its ability. Sound knowledge of techniques that can be used for maintaining legacy systems can help you avoid common pitfalls. The book begins with a quick overview of what a real legacy system looks like, how it works, and common issues that may be faced when trying to maintaining it. You'll then explore the architecture of a legacy system in detail and understand each of its components. As you progress, you'll discover a variety of techniques for analyzing a legacy system and how to apply them. Once you get to grips with the security constraints associated with legacy systems, you'll explore ways to secure them. Finally, you'll be able to easily make changes in legacy systems to enhance their performance. By the end of this book, you’ll have developed the skills and confidence to work with legacy systems and efficiently maintain them.
Table of Contents (7 chapters)

Stabilization


Why Stability?

Many systems can suffer from instability and fragility. Legacy systems are particularly prone to these problems for two main reasons:

  • Complex systems require maintenance, and without it, the system degrades.

  • Continual modifications can add complexity and inconsistency.

These can be viewed as a kind of entropy (I know physicists are yelling that it's not really entropy but IT systems do tend toward disorder unless work is performed) and the longer a system exists, the greater the effect. If you're lucky, then your legacy system will have received all the maintenance required, but then you wouldn't have bought this book.

I would always suggest performing a stabilization phase when working with a legacy system – even if you intend to replace it. If the system is stable, then you will not be constantly pestered by user complaints.

Note

Stabilizing a system due to be replaced is not wasted effort, as it removes distractions

Not only will a stable system reduce your distractions...