Skip to main content

> Term

architecture drift

The gradual divergence between a system's documented, intended design and its actual implementation in production.

Detailed Explanation

The gradual divergence between a system's documented, intended design and its actual implementation in production. It happens one small hotfix, urgent feature, or temporary workaround at a time.

Over months or years, the mental model of the system no longer matches the operational reality, turning once-safe assumptions into dangerous blind spots.

Why It Matters

It invalidates previous design decisions and security assumptions, making future changes unpredictable and significantly increasing system debt.

Common Failure Mode

An incident occurs because an engineer relied on an architecture diagram that hadn't been updated to reflect the three 'temporary' message queues added last quarter.

Practical Example

A strictly layered microservice architecture slowly drifts as teams start sharing a common database to avoid the latency of API calls.

Production Manifestation

Undocumented direct database connections bypassing the API layer, hardcoded IP addresses, and services communicating outside of defined boundaries.

Frequently Asked Questions

What is architecture drift in short?

The gradual divergence between a system's documented, intended design and its actual implementation in production.

What is the most common failure mode?

An incident occurs because an engineer relied on an architecture diagram that hadn't been updated to reflect the three 'temporary' message queues added last quarter.

AI Summary

The gradual divergence between a system's documented, intended design and its actual implementation in production. It invalidates previous design decisions and security assumptions, making future changes unpredictable and significantly increasing system debt.