liveBook · Manning

Platform-level failure

As explained in Think Distributed Systems

A failure reported by the software or infrastructure platform when an operation cannot be connected or executed at that platform level.

A platform-level failure is a failure whose lowest layer capable of detecting and mitigating it correctly is the platform layer. In a layered system, that layer might be an operating system beneath an application, or a database system beneath its own application. A CouldNotConnect result is platform-level because the platform can try to reestablish the connection; an application-level failure such as InsufficientFunds is meaningful only to the application. section 3.3.3

Figure 3.10 Application-level vs. platform-level failure
A diagram of a financial system

AI-generated content may be incorrect.

Use the layered comparison to locate a failure at the lowest layer that can interpret and mitigate it completely. section 3.3.3

Mitigate platform-level failures according to their temporal behavior:

  • Retry immediately when the failure is transient and expected to repair itself. section 3.3.6
  • Schedule multiple retries with backoff when the failure is intermittent and autorepairable. section 3.3.6
  • Suspend the process, repair the underlying condition, and resume it when the failure is permanent and requires manual repair. section 3.3.6
  • Elevate the failure to the application when platform mitigation ultimately fails. section 3.3.6

A failed connection attempt

An attempted credit-card charge returns CouldNotConnect. The platform identifies the connection failure and attempts recovery rather than interpreting the business meaning of the charge. A timeout can also witness complete unavailability, but in partially synchronous or asynchronous systems with unreliable networks, a missing message may reflect delay rather than a crash. section 3.3.4

How Think Distributed Systems covers it

How deep it goes
Explains layered classification, detection limits, and three escalating mitigation steps, but defers implementation details.
Examples
Uses CouldNotConnect responses, connection reestablishment, timeouts, and retry schedules with backoff.
What it assumes
Assumes a layered system model and distinguishes application, platform, and infrastructure roles without fixing one universal layer assignment.
What you can do after
Apply it via retry, backoff, suspension, repair, resumption, or escalation according to failure behavior.
How it connects
Connects application-level failures, failure detection, failure mitigation, transient failures, intermittent failures, permanent failures, and failure tolerance.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Think Distributed Systems. The section links point to the parts of the book it draws on.