@@ -18,47 +18,50 @@ page.
1818
1919## How the set is organized
2020
21- The ten pages fall into four movements. The ** conceptual grounding** (pages 1–2 )
22- establishes what a data mesh is and why Kubernetes is a natural substrate for one. The
23- ** implementation** (pages 3–8 ) builds the system: the services and their data products,
24- the contracts and catalog that make them discoverable , the data planes they communicate
25- over, progressive delivery with mutual TLS, elastic scaling and recovery, and the
26- observability to see it all. The ** failure modes ** (page 9) steps back to the
27- conceptual and organizational anti-patterns that derail data-mesh efforts even when
28- the technology is sound. The ** summary** (page 10) closes by reorganizing the same
29- material by principle — for each of the four principles, the value it delivers and the
30- implementation pieces that realize it.
21+ The eleven pages fall into four movements. The ** conceptual grounding** (pages 1–3 )
22+ establishes the landscape of data architectures, what a data mesh is, and why Kubernetes
23+ is a natural substrate for one. The ** implementation** (pages 4–9 ) builds the system:
24+ the services and their data products , the contracts and catalog that make them
25+ discoverable, the data planes they communicate over, progressive delivery with mutual
26+ TLS, elastic scaling and recovery, and the observability to see it all. The ** failure
27+ modes ** (page 10) steps back to the conceptual and organizational anti-patterns that
28+ derail data-mesh efforts even when the technology is sound. The ** summary** (page 11)
29+ closes by reorganizing the same material by principle — for each of the four principles,
30+ the value it delivers and the implementation pieces that realize it.
3131
3232## The pages
3333
34- - [ ** 1 · Concepts & principles** ] ({{ '/docs/01-concepts/' | relative_url }}) —
34+ - [ ** 1 · Data architectures** ] ({{ '/docs/01-data-architectures/' | relative_url }}) —
35+ The landscape from pipelines to lakes to mesh — what each pattern is, the problem
36+ it solves, and why the mesh is a different kind of answer.
37+ - [ ** 2 · Concepts & principles** ] ({{ '/docs/01-concepts/' | relative_url }}) —
3538 What a data mesh is, operational versus analytical data, and Dehghani's four
3639 principles. The grounding before any commands.
37- - [ ** 2 · Kubernetes as the substrate** ] ({{ '/docs/02-kubernetes-substrate/' | relative_url }}) —
40+ - [ ** 3 · Kubernetes as the substrate** ] ({{ '/docs/02-kubernetes-substrate/' | relative_url }}) —
3841 Why the four principles map cleanly onto namespaces, operators, RBAC, and platform
3942 primitives, and the shape of the system you'll build.
40- - [ ** 3 · Services & data products** ] ({{ '/docs/03-services-and-data-products/' | relative_url }}) —
43+ - [ ** 4 · Services & data products** ] ({{ '/docs/03-services-and-data-products/' | relative_url }}) —
4144 The anatomy of a data product, the five domain services plus the gateway, and the
4245 order-service template the others follow.
43- - [ ** 4 · Contracts & the catalog** ] ({{ '/docs/04-contracts-and-catalog/' | relative_url }}) —
46+ - [ ** 5 · Contracts & the catalog** ] ({{ '/docs/04-contracts-and-catalog/' | relative_url }}) —
4447 Versioned contracts in a registry, the runtime-versus-discovery distinction, and why a
4548 catalog is a mesh requirement rather than an add-on.
46- - [ ** 5 · The data planes** ] ({{ '/docs/05-data-planes/' | relative_url }}) —
49+ - [ ** 6 · The data planes** ] ({{ '/docs/05-data-planes/' | relative_url }}) —
4750 The synchronous read layer (REST, gRPC, a GraphQL gateway) and the asynchronous event
4851 backbone — and why the capstone uses all of them.
49- - [ ** 6 · Progressive delivery & mTLS** ] ({{ '/docs/06-progressive-delivery-mtls/' | relative_url }}) —
52+ - [ ** 7 · Progressive delivery & mTLS** ] ({{ '/docs/06-progressive-delivery-mtls/' | relative_url }}) —
5053 Evolving a contract in the open with a v1→v2 canary, mTLS for free, and the decision to
5154 mesh selectively rather than namespace-wide.
52- - [ ** 7 · Elastic & resilient** ] ({{ '/docs/07-elastic-and-resilient/' | relative_url }}) —
55+ - [ ** 8 · Elastic & resilient** ] ({{ '/docs/07-elastic-and-resilient/' | relative_url }}) —
5356 Scaling to demand and to zero with KEDA, and the cloud-native recoverability the
5457 platform provides.
55- - [ ** 8 · Observability** ] ({{ '/docs/08-observability/' | relative_url }}) —
58+ - [ ** 9 · Observability** ] ({{ '/docs/08-observability/' | relative_url }}) —
5659 Metrics, distributed traces across products, and the live view of traffic moving
5760 through the mesh.
58- - [ ** 9 · Anti-patterns** ] ({{ '/docs/09-anti-patterns/' | relative_url }}) —
61+ - [ ** 10 · Anti-patterns** ] ({{ '/docs/09-anti-patterns/' | relative_url }}) —
5962 The conceptual and organizational ways data-mesh efforts go wrong, drawn from the
6063 literature, so you can recognize them early.
61- - [ ** 10 · Summary** ] ({{ '/docs/10-summary/' | relative_url }}) —
64+ - [ ** 11 · Summary** ] ({{ '/docs/10-summary/' | relative_url }}) —
6265 Each principle, reorganized: the value it delivers, the implementation pieces that
6366 realize it, and the failure mode when it's missing.
6467
0 commit comments