Knowledge/Domain
Modeling, storing, and publishing information.
Drag to pan · hold ⌘/ctrl and scroll — or pinch — to zoom.
Making content discoverable through search, most of which is ordinary quality work.
Data & Content·16 connections
A versioned, ordered change to a database schema, applied once and recorded.
Data & Content·13 connections
How information is organized, labeled, and navigated so people can find what they need.
Data organized as tables with declared relationships, queried declaratively and guarded by constraints.
A runtime switch that decouples shipping code from enabling behavior.
Data & Content·12 connections
A plain-text formatting syntax designed to be readable as written, now the default for technical writing.
Data & Content·11 connections
Divergence between a schema and the code, types, or documentation that describe it.
A metadata block at the top of a text document, separated from the body by delimiters.
Data & Content·10 connections
A syndication format letting readers subscribe to a site without an intermediary.
Machine-readable markup describing what a page is about, in a shared vocabulary.
The four guarantees a transactional database makes so concurrent, interrupted work never leaves data half-done.
Data & Content·9 connections
When a network splits a distributed system, it can stay consistent or stay available, but a proven theorem says not both.
A content system exposing structured data through an API, with presentation left entirely to consumers.
One deployment serving many isolated customers, with tenancy threaded through data, routing, and access.
A protocol for committing one transaction across multiple databases atomically, at the cost of blocking if the coordinator dies.
Turning a database's own internal write log into a stream other systems can subscribe to, without touching the application.
Data & Content·8 connections
Copying the same data to multiple database nodes for redundancy and read scale, at the cost of a lag window.
Initial content created programmatically to make an empty system usable or demonstrable.
A buffer that decouples a producer from a consumer in time, so neither has to be up, fast, or reachable at the same moment.
Data & Content·7 connections
Splitting one dataset across multiple databases by key, trading a single point of scale for cross-shard complexity.
Data & Content·6 connections
Keeping an in-progress version of content separate from the live one, with all the state that implies.
Data & Content·5 connections
Storing every change that ever happened, instead of only the current state, so the current state becomes a derived view.
Letting concurrent writers proceed unchecked and catching conflicts only at commit time, betting that collisions are rare.
A cache that acknowledges a write immediately and persists it to the real store later, trading durability for write latency.
A protocol that gets a majority of unreliable, independent nodes to agree on one value, surviving any minority failing.
Data & Content·4 connections
Deliberately duplicating data to make reads faster, trading update complexity for query simplicity.
The process a distributed system uses to pick one node to coordinate, and to notice and replace it when it dies.
Blocking every other writer up front for the duration of a transaction, betting that collisions are common enough to prevent rather than clean up.