Computing.

Software systems, algorithms, infrastructure, data, and the ideas connecting them.

6 reference pagesHierarchical field map

Computing is a fixture map of a field rather than a folder tree. The areas below are navigation scaffolding: they can deepen, split, or be renamed without changing the stable URL of a page.

The guided path is deliberately small. It is useful when a reader wants an order, but it is not the default way to browse the whole domain.

01 / Map of the field

Areas and subareas.

Hierarchy provides orientation and can deepen over time without changing a document’s canonical URL.

Systems

Boundaries, coordination, messaging, and reliability in systems that change over time.

5 pages

Distributed Systems

Models for reasoning about independent components, communication, and failure.

2 pages

conceptReasoning about distributed systems boundariesA compact mental model for identifying where independently changing components become a distributed-systems problem.conceptSystem boundariesA short reference for locating the boundary at which independently changing parts need an explicit contract.

Messaging

Delivery, retries, ordering, and the contracts around messages.

2 pages

referenceIdempotency as a system propertyA reference for designing repeated requests so retries do not create repeated effects.referenceMessage delivery semanticsA reference for distinguishing delivery guarantees from the application behavior built on top of them.

Reliability

Failure domains, operational signals, and recoverable system behavior.

1 page

guideFailure domainsA guide to naming which parts of a system can fail together and which consequences cross the boundary.

Software

Design and implementation ideas for making software easier to change.

0 pages

Data

Structures and transformations that make information useful to systems.

0 pages

Infrastructure

The runtime foundations around applications, networks, and delivery.

1 page

overviewContainer networking mental modelAn overview of the names, interfaces, and boundaries that shape communication between containers.

02 / Optional guided path

If you’re new to Computing.

A curated sequence for readers who want progression. It is optional, not a chronology.

01Start with boundariesA short reference for locating the boundary at which independently changing parts need an explicit contract.02Model independent changeA compact mental model for identifying where independently changing components become a distributed-systems problem.03Make retries safeA reference for designing repeated requests so retries do not create repeated effects.04Name the failure surfaceA guide to naming which parts of a system can fail together and which consequences cross the boundary.

03 / Entry points

Useful starting points.

Manually selected pages for this area, independent of recency or popularity.

Concept · Systems · Distributed SystemsReasoning about distributed systems boundariesA compact mental model for identifying where independently changing components become a distributed-systems problem.Reference · Systems · MessagingIdempotency as a system propertyA reference for designing repeated requests so retries do not create repeated effects.Overview · InfrastructureContainer networking mental modelAn overview of the names, interfaces, and boundaries that shape communication between containers.

Atlas context

Nearby in the public corpus.

This artifact is highlighted; connected nodes are reviewed relations.

Explore the full atlas →

overview · 72%