Background

This section covers cross-cutting initiatives and rationale that don't fit cleanly under a single feature page. They explain why parts of the codebase look the way they do.

Pages

• Modularity — the long-running module API hygiene effort.

Other context worth knowing

The repository carries dedicated design documents for several major features. They are not duplicated in this wiki; instead, the relevant feature page links to them.

Topic	Reference
Logging	docs/logging.md, docs/parsing_stack_traces.md
Exception architecture	docs/exception_architecture.md
Futures and promises	docs/futures_and_promises.md
Batons	docs/baton.md
Change streams	docs/change_streams.md
IDL	docs/idl.md
Server parameters	docs/server_parameters.md
Egress networking	docs/egress_networking.md
Modularity	docs/modularity.md, Modularity wiki page
Primary-only services	docs/primary_only_service.md
Fail points	docs/fail_points.md
Memory management	docs/memory_management.md
C++ style	docs/cpp_style.md
Devcontainer	docs/devcontainer-setup.md
Golden data tests	docs/golden_data_test_framework.md
Fuzzers	docs/fuzztest.md, docs/libfuzzer.md
Load balancer support	docs/load_balancer_support.md
Priority port	docs/priority_port.md
Read/write mutex	docs/rwmutex.md
Thread pools	docs/thread_pools.md

The Lore page lays out the historical timeline of major rewrites.