|
1 | 1 | --- |
2 | 2 | title: "The data mesh: start here" |
3 | 3 | order: 0 |
4 | | -description: "The map: what this reference builds, the reading order, and a link to each page in the set. Start here." |
| 4 | +description: "The map: what this reference builds, the reading order, and a link to each chapter in the set. Start here." |
5 | 5 | duration: 5 min |
6 | 6 | --- |
7 | 7 |
|
8 | 8 | ## Learning objectives |
9 | 9 |
|
10 | 10 | By the end of this chapter you can: |
11 | 11 |
|
12 | | -- Name the four movements the reference set is organized into and which pages fall |
| 12 | +- Name the four movements the reference set is organized into and which chapters fall |
13 | 13 | into each one. |
14 | 14 | - Pick the reading order that matches how you want to use the set: straight through, |
15 | 15 | or jumping to one topic. |
16 | | -- Identify the three pages that cover the pattern's shape if you only have time for a |
| 16 | +- Identify the three chapters that cover the pattern's shape if you only have time for a |
17 | 17 | few. |
18 | | -- Locate the page that answers a specific question without re-reading the whole set. |
| 18 | +- Locate the chapter that answers a specific question without re-reading the whole set. |
19 | 19 |
|
20 | 20 | ## Why this matters |
21 | 21 |
|
22 | | -Page 2 names Dehghani's four principles. Page 3 takes the same four and maps each one |
| 22 | +Chapter 2 names Dehghani's four principles. Chapter 3 takes the same four and maps each one |
23 | 23 | to a Kubernetes primitive: namespaces, operators, RBAC. That's the shape of this whole |
24 | 24 | set. A concept gets introduced, then you watch it land in a running piece of the |
25 | | -system a few pages later. This page is the map, nothing more: what the reference |
26 | | -covers, the order to read it in, and a link to each page. |
| 25 | +system a few chapters later. This chapter is the map, nothing more: what the reference |
| 26 | +covers, the order to read it in, and a link to each chapter. |
27 | 27 |
|
28 | 28 | The reference builds one working system end to end. A data mesh of services that own |
29 | 29 | their data as products, that talk over a deliberate mix of protocols, that evolve their |
30 | 30 | contracts safely, that scale to demand, and that stay observable throughout. |
31 | 31 |
|
32 | | -Read it straight through the first time if you can. Each page picks up where the last |
| 32 | +Read it straight through the first time if you can. Each chapter picks up where the last |
33 | 33 | left off, and the cross-references assume you've seen the earlier material. If you're |
34 | 34 | back here looking for one specific thing, the descriptions below point at the right |
35 | | -page. |
| 35 | +chapter. |
36 | 36 |
|
37 | 37 | ## How the set is organized |
38 | 38 |
|
39 | | -The eleven pages fall into four movements. **Conceptual grounding** (pages 1 to 3) |
| 39 | +The eleven chapters fall into four movements. **Conceptual grounding** (chapters 1 to 3) |
40 | 40 | covers the landscape of data architectures, what a data mesh actually is, and why |
41 | | -Kubernetes turns out to be a natural substrate for one. **Implementation** (pages 4 to |
| 41 | +Kubernetes turns out to be a natural substrate for one. **Implementation** (chapters 4 to |
42 | 42 | 9) builds the system: the services and their data products, the contracts and catalog |
43 | 43 | that make them discoverable, the data planes they talk over, progressive delivery with |
44 | 44 | mutual TLS, elastic scaling and recovery, and the observability to see all of it. |
45 | | -**Failure modes** (page 10) steps back to the conceptual and organizational |
| 45 | +**Failure modes** (chapter 10) steps back to the conceptual and organizational |
46 | 46 | anti-patterns that derail data-mesh efforts even when the technology is sound. The |
47 | | -**summary** (page 11) closes by reorganizing the same material by principle: for each |
| 47 | +**summary** (chapter 11) closes by reorganizing the same material by principle: for each |
48 | 48 | of the four, the value it delivers and the implementation pieces that realize it. |
49 | 49 |
|
50 | | -## The pages |
| 50 | +## The chapters |
51 | 51 |
|
52 | 52 | - [**1 · Data architectures**]({{ '/docs/01-data-architectures/' | relative_url }}): |
53 | 53 | the landscape from pipelines to lakes to mesh, what each pattern is, the problem |
@@ -96,12 +96,12 @@ Start with [concepts & principles]({{ '/docs/01-concepts/' | relative_url }}). |
96 | 96 |
|
97 | 97 | ## For deeper coverage |
98 | 98 |
|
99 | | -- *Data Mesh* by Zhamak Dehghani: the full argument this reference implements, including |
| 99 | +- [*Data Mesh*](https://www.oreilly.com/library/view/data-mesh/9781492092384/) by Zhamak Dehghani: the full argument this reference implements, including |
100 | 100 | the history and the operating-model shifts this set only summarizes. |
101 | | -- *Designing Data-Intensive Applications, 2nd ed.* by Martin Kleppmann & Chris |
| 101 | +- [*Designing Data-Intensive Applications, 2nd ed.*](https://www.oreilly.com/library/view/designing-data-intensive-applications/9781098119058/) by Martin Kleppmann & Chris |
102 | 102 | Riccomini: the data-systems foundations (storage, replication, consistency) that sit |
103 | 103 | underneath every data product in this build. |
104 | | -- *Cloud Native Patterns* by Cornelia Davis: the platform patterns this reference's |
| 104 | +- [*Cloud Native Patterns*](https://www.manning.com/books/cloud-native-patterns) by Cornelia Davis: the platform patterns this reference's |
105 | 105 | self-serve tier draws on. |
106 | | -- *Kubernetes Patterns* by Bilgin Ibryam & Roland Huß: the Kubernetes-native building |
107 | | - blocks the implementation pages rely on throughout. |
| 106 | +- [*Kubernetes Patterns*](https://www.oreilly.com/library/view/-/9781098131678/) by Bilgin Ibryam & Roland Huß: the Kubernetes-native building |
| 107 | + blocks the implementation chapters rely on throughout. |
0 commit comments