Cloudthe Labs / Independent engineering
Fig Cloud LabLab network
Menu

Cloudthe Labs

The model and the field.

Two publications, one engineering notebook. Fig develops the explanations and design choices; Nether follows them into reproducible procedures and operational checks.

01 / The foundations

Fig Cloud Lab

Read the architecture study first: the question, the system model, the useful guarantees, and their limits.

Browse Fig articlesfig.cloudthe.me
02 / The practical continuation

Nether Cloud Lab

Then try a bounded procedure: the environment, checks, expected observations, failure handling, and cleanup.

Browse Nether articlesnether.cloudthe.me

Paired reading paths

Start with a question.

Linux networking

Fig / FoundationsLinux Network Namespaces ExplainedNether / PracticeA Reproducible Namespace Routing Lab

Service health

Fig / FoundationsUnderstanding Service Health ChecksNether / PracticeHealth Check Failure Drills

Observability

Fig / FoundationsObservability for Small Distributed SystemsNether / PracticeAn Observability Budget for a Small Host

Containers

Fig / FoundationsContainers and Process IsolationNether / PracticeRunning Containers on Small Hosts

Edge computing

Fig / FoundationsEdge Computing Architecture PatternsNether / PracticeBounded Telemetry Buffering at the Edge

Background work

Fig / FoundationsDesigning Reliable Background WorkersNether / PracticeA Background Worker Recovery Playbook

A shared editorial method

Guides separate explanations from measurements. A command or an expected outcome is a proposed check, not evidence that a live environment has been tested. Project pages describe design studies and test plans; measured results belong in a dated note with an explicit setup.

Each lab has its own article archive, canonical URLs and RSS feed. Companion links connect the two editions without republishing the same article under a different domain.