Skip to main content

> Term

legacy system

Old or outdated software that remains in production because it supports critical business functions.

Detailed Explanation

An outdated, poorly documented, or technologically obsolete software system that remains in active use because the business fundamentally relies on it.

Legacy systems are often feared by developers but are deeply respected by the business, as they are usually the systems actually generating revenue.

Why It Matters

It acts as an anchor on engineering velocity. Modifying a legacy system carries immense risk, yet failing to modernize it eventually leads to unmaintainable tech debt.

Common Failure Mode

A seemingly minor update to a modern microservice breaks the legacy monolith, because the monolith was secretly relying on a specific, undocumented data format.

Practical Example

A ten-year-old monolithic Java application that processes 100% of the company's daily transactions but has zero automated tests and no original authors left.

Production Manifestation

Monolithic architectures, obsolete framework versions, single massive databases, and code nobody dares to refactor.

Frequently Asked Questions

What is legacy system in short?

Old or outdated software that remains in production because it supports critical business functions.

What is the most common failure mode?

A seemingly minor update to a modern microservice breaks the legacy monolith, because the monolith was secretly relying on a specific, undocumented data format.

AI Summary

Old or outdated software that remains in production because it supports critical business functions. It acts as an anchor on engineering velocity. Modifying a legacy system carries immense risk, yet failing to modernize it eventually leads to unmaintainable tech debt.