Runtime Dependence

Runtime dependence describes how much a website relies on active systems at the moment a page is served.
It determines whether a site can function with minimal infrastructure or requires continuous coordination between components.

This decision influences reliability, failure modes, and tolerance for interruption.
Its consequences are structural rather than experiential.

Decision Space

Runtime dependence ranges from sites that serve precomputed files to systems that assemble responses dynamically.
Most architectures combine both, but one mode usually dominates.

The tradeoff is between immediacy and resilience.

Low Runtime Dependence

In a low-dependence model, pages are delivered with little or no runtime logic.
External systems are not required for basic access.

• High reliability under partial failure
• Predictable performance
• Limited responsiveness to real-time data

Change requires regeneration rather than recalculation.
The system is slow to adapt but stable once deployed.

High Runtime Dependence

In a high-dependence model, pages are assembled at request time.
Content, layout, or behavior depends on databases, APIs, or application logic.

• Immediate reflection of state changes
• Greater flexibility and interactivity
• Increased failure surface

Partial outages can render the site unusable.
Operational reliability becomes a continuous concern.

Persistent Tradeoffs

Low runtime dependence favors durability and simplicity.
High runtime dependence favors responsiveness and capability.

The decision determines whether failure is silent and local or visible and systemic.
Reversing direction later is rarely trivial.