
The principles of extreme fault tolerance
PlanetScale emphasizes its extreme fault tolerance through foundational principles and a robust architecture. The system is designed to isolate failures and ensure redundancy, allowing continued operation even during issues. Their processes, including automatic failovers and synchronous replication, further enhance reliability and minimize disruptions for customers.
- ▪PlanetScale utilizes a shared nothing architecture to enhance speed and reliability.
- ▪The system's fault tolerance is based on principles such as isolation, redundancy, and static stability.
- ▪Automatic failovers and synchronous replication are key processes that reinforce the system's overall fault tolerance.
Hacker News (Newest) files mainly under programming. We currently carry 5,306 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Planetscale |
| Canonical URL | https://planetscale.com/blog/the-principles-of-extreme-fault-tolerance |
| Publication time | Sun, 24 May 2026 22:22:29 +0000 |
| Retrieval time | 2026-05-24T22:37:34.934Z |
| Last seen | 2026-05-24T22:37:34.934Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | WR5jnBb3NFjJ |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
The principles of extreme fault toleranceMax Englander | July 3, 2025PlanetScale is fast and reliable. Our speed is the best in the cloud due to our shared nothing architecture that enables us to utilize local storage instead of network-attached storage. Our fault tolerance is built on top of principles, processes, and architectures that are easy to understand, but require painstaking work to do well.We have talked about our speed a lot. Let's talk about why we are reliable.PrinciplesOur principles are neither new nor radical. You may find them obvious. Even so, they are foundational for our fault tolerance.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Planetscale.