.NET Day 2024: Five common mistakes with distributed systems

More info at: https://dotnetday.ch

Transcript

2. Adam Ralph Five common mistakes with distributed systems I’ve made them all!
6. MONOLITH
8. var service = new MyService(); var result = service.Process(data);
9. Event Latency Scaled 1 CPU cycle (3.7 MHz) 0.3 ns 1 s Level 1 cache access 1 ns 3 s Level 2 cache access 3 ns 9 s Level 3 cache access 12 ns 36 s Main memory access (SDRAM) 120 ns 6 min SSD I/O 50–150 µs 2–6 days HDD I/O 1–10 ms 1–12 months Internet: San Francisco to New York 40 ms 4 years Internet: San Francisco to London 81 ms 8 years Internet: San Francisco to Sydney 183 ms 20 years TCP packet retransmit 1–3 s 100–300 years OS virtualisation system reboot 4 s 400 years SCSI command time-out 30 s 3 millenia Hardware virtualisation system reboot 40 s 4 millenia Physical system reboot 2 min 12 millenia
10. Event Latency Scaled 1 CPU cycle (3.7 MHz) 0.3 ns 1 s Level 1 cache access 1 ns 3 s Level 2 cache access 3 ns 9 s Level 3 cache access 12 ns 36 s Main memory access (SDRAM) 120 ns 6 min SSD I/O 50–150 µs 2–6 days HDD I/O 1–10 ms 1–12 months Internet: San Francisco to New York 40 ms 4 years Internet: San Francisco to London 81 ms 8 years Internet: San Francisco to Sydney 183 ms 20 years TCP packet retransmit 1–3 s 100–300 years OS virtualisation system reboot 4 s 400 years SCSI command time-out 30 s 3 millenia Hardware virtualisation system reboot 40 s 4 millenia Physical system reboot 2 min 12 millenia
11. Event Latency Scaled 1 CPU cycle (3.7 MHz) 0.3 ns 1 s Level 1 cache access 1 ns 3 s Level 2 cache access 3 ns 9 s Level 3 cache access 12 ns 36 s Main memory access (SDRAM) 120 ns 6 min SSD I/O 50–150 µs 2–6 days HDD I/O 1–10 ms 1–12 months Internet: San Francisco to New York 40 ms 4 years Internet: San Francisco to London 81 ms 8 years Internet: San Francisco to Sydney 183 ms 20 years TCP packet retransmit 1–3 s 100–300 years OS virtualisation system reboot 4 s 400 years SCSI command time-out 30 s 3 millenia Hardware virtualisation system reboot 40 s 4 millenia Physical system reboot 2 min 12 millenia
12. Event Latency Scaled 1 CPU cycle (3.7 MHz) 0.3 ns 1 s Level 1 cache access 1 ns 3 s Level 2 cache access 3 ns 9 s Level 3 cache access 12 ns 36 s Main memory access (SDRAM) 120 ns 6 min SSD I/O 50–150 µs 2–6 days HDD I/O 1–10 ms 1–12 months Internet: San Francisco to New York 40 ms 4 years Internet: San Francisco to London 81 ms 8 years Internet: San Francisco to Sydney 183 ms 20 years TCP packet retransmit 1–3 s 100–300 years OS virtualisation system reboot 4 s 400 years SCSI command time-out 30 s 3 millenia Hardware virtualisation system reboot 40 s 4 millenia Physical system reboot 2 min 12 millenia
13. Event Latency Scaled 1 CPU cycle (3.7 MHz) 0.3 ns 1 s Level 1 cache access 1 ns 3 s Level 2 cache access 3 ns 9 s Level 3 cache access 12 ns 36 s Main memory access (SDRAM) 120 ns 6 min SSD I/O 50–150 µs 2–6 days HDD I/O 1–10 ms 1–12 months Internet: San Francisco to New York 40 ms 4 years Internet: San Francisco to London 81 ms 8 years Internet: San Francisco to Sydney 183 ms 20 years TCP packet retransmit 1–3 s 100–300 years OS virtualisation system reboot 4 s 400 years SCSI command time-out 30 s 3 millenia Hardware virtualisation system reboot 40 s 4 millenia Physical system reboot 2 min 12 millenia
14. Event Latency Scaled 1 CPU cycle (3.7 MHz) 0.3 ns 1 s Level 1 cache access 1 ns 3 s Level 2 cache access 3 ns 9 s Level 3 cache access 12 ns 36 s Main memory access (SDRAM) 120 ns 6 min SSD I/O 50–150 µs 2–6 days HDD I/O 1–10 ms 1–12 months Internet: San Francisco to New York 40 ms 4 years Internet: San Francisco to London 81 ms 8 years Internet: San Francisco to Sydney 183 ms 20 years TCP packet retransmit 1–3 s 100–300 years OS virtualisation system reboot 4 s 400 years SCSI command time-out 30 s 3 millenia Hardware virtualisation system reboot 40 s 4 millenia Physical system reboot 2 min 12 millenia
15. Event Latency Scaled 1 CPU cycle (3.7 MHz) 0.3 ns 1 s Level 1 cache access 1 ns 3 s Level 2 cache access 3 ns 9 s Level 3 cache access 12 ns 36 s Main memory access (SDRAM) 120 ns 6 min SSD I/O 50–150 µs 2–6 days HDD I/O 1–10 ms 1–12 months Internet: San Francisco to New York 40 ms 4 years Internet: San Francisco to London 81 ms 8 years Internet: San Francisco to Sydney 183 ms 20 years TCP packet retransmit 1–3 s 100–300 years OS virtualisation system reboot 4 s 400 years SCSI command time-out 30 s 3 millenia Hardware virtualisation system reboot 40 s 4 millenia Physical system reboot 2 min 12 millenia
16. Event Latency Scaled 1 CPU cycle (3.7 MHz) 0.3 ns 1 s Level 1 cache access 1 ns 3 s Level 2 cache access 3 ns 9 s Level 3 cache access 12 ns 36 s Main memory access (SDRAM) 120 ns 6 min SSD I/O 50–150 µs 2–6 days HDD I/O 1–10 ms 1–12 months Internet: San Francisco to New York 40 ms 4 years Internet: San Francisco to London 81 ms 8 years Internet: San Francisco to Sydney 183 ms 20 years TCP packet retransmit 1–3 s 100–300 years OS virtualisation system reboot 4 s 400 years SCSI command time-out 30 s 3 millenia Hardware virtualisation system reboot 40 s 4 millenia Physical system reboot 2 min 12 millenia
17. Event Latency Scaled 1 CPU cycle (3.7 MHz) 0.3 ns 1 s Level 1 cache access 1 ns 3 s Level 2 cache access 3 ns 9 s Level 3 cache access 12 ns 36 s Main memory access (SDRAM) 120 ns 6 min SSD I/O 50–150 µs 2–6 days HDD I/O 1–10 ms 1–12 months Internet: San Francisco to New York 40 ms 4 years Internet: San Francisco to London 81 ms 8 years Internet: San Francisco to Sydney 183 ms 20 years TCP packet retransmit 1–3 s 100–300 years OS virtualisation system reboot 4 s 400 years SCSI command time-out 30 s 3 millenia Hardware virtualisation system reboot 40 s 4 millenia Physical system reboot 2 min 12 millenia
18. var service = new MyService(); var result = service.Process(data);
19. Event Latency Scaled 1 CPU cycle (3.7 MHz) 0.3 ns 1 s Level 1 cache access 1 ns 3 s Level 2 cache access 3 ns 9 s Level 3 cache access 12 ns 36 s Main memory access (SDRAM) 120 ns 6 min SSD I/O 50–150 µs 2–6 days HDD I/O 1–10 ms 1–12 months Internet: San Francisco to New York 40 ms 4 years Internet: San Francisco to London 81 ms 8 years Internet: San Francisco to Sydney 183 ms 20 years TCP packet retransmit 1–3 s 100–300 years OS virtualisation system reboot 4 s 400 years SCSI command time-out 30 s 3 millenia Hardware virtualisation system reboot 40 s 4 millenia Physical system reboot 2 min 12 millenia
20. Event Latency Scaled 1 CPU cycle (3.7 MHz) 0.3 ns 1 s Level 1 cache access 1 ns 3 s Level 2 cache access 3 ns 9 s Level 3 cache access 12 ns 36 s Main memory access (SDRAM) 120 ns 6 min SSD I/O 50–150 µs 2–6 days HDD I/O 1–10 ms 1–12 months Internet: San Francisco to New York 40 ms 4 years Internet: San Francisco to London 81 ms 8 years Internet: San Francisco to Sydney 183 ms 20 years TCP packet retransmit 1–3 s 100–300 years OS virtualisation system reboot 4 s 400 years SCSI command time-out 30 s 3 millenia Hardware virtualisation system reboot 40 s 4 millenia Physical system reboot 2 min 12 millenia
21. Event Latency Scaled 1 CPU cycle (3.7 MHz) 0.3 ns 1 s Level 1 cache access 1 ns 3 s Level 2 cache access 3 ns 9 s Level 3 cache access 12 ns 36 s Main memory access (SDRAM) 120 ns 6 min SSD I/O 50–150 µs 2–6 days HDD I/O 1–10 ms 1–12 months Internet: San Francisco to New York 40 ms 4 years Internet: San Francisco to London 81 ms 8 years Internet: San Francisco to Sydney 183 ms 20 years TCP packet retransmit 1–3 s 100–300 years OS virtualisation system reboot 4 s 400 years SCSI command time-out 30 s 3 millenia Hardware virtualisation system reboot 40 s 4 millenia Physical system reboot 2 min 12 millenia
22. Event Latency Scaled 1 CPU cycle (3.7 MHz) 0.3 ns 1 s Level 1 cache access 1 ns 3 s Level 2 cache access 3 ns 9 s Level 3 cache access 12 ns 36 s Main memory access (SDRAM) 120 ns 6 min SSD I/O 50–150 µs 2–6 days HDD I/O 1–10 ms 1–12 months Internet: San Francisco to New York 40 ms 4 years Internet: San Francisco to London 81 ms 8 years Internet: San Francisco to Sydney 183 ms 20 years TCP packet retransmit 1–3 s 100–300 years OS virtualisation system reboot 4 s 400 years SCSI command time-out 30 s 3 millenia Hardware virtualisation system reboot 40 s 4 millenia Physical system reboot 2 min 12 millenia
23. Event Latency Scaled 1 CPU cycle (3.7 MHz) 0.3 ns 1 s Level 1 cache access 1 ns 3 s Level 2 cache access 3 ns 9 s Level 3 cache access 12 ns 36 s Main memory access (SDRAM) 120 ns 6 min SSD I/O 50–150 µs 2–6 days HDD I/O 1–10 ms 1–12 months Internet: San Francisco to New York 40 ms 4 years Internet: San Francisco to London 81 ms 8 years Internet: San Francisco to Sydney 183 ms 20 years TCP packet retransmit 1–3 s 100–300 years OS virtualisation system reboot 4 s 400 years SCSI command time-out 30 s 3 millenia Hardware virtualisation system reboot 40 s 4 millenia Physical system reboot 2 min 12 millenia
24. Event Latency Scaled 1 CPU cycle (3.7 MHz) 0.3 ns 1 s Level 1 cache access 1 ns 3 s Level 2 cache access 3 ns 9 s Level 3 cache access 12 ns 36 s Main memory access (SDRAM) 120 ns 6 min SSD I/O 50–150 µs 2–6 days HDD I/O 1–10 ms 1–12 months Internet: San Francisco to New York 40 ms 4 years Internet: San Francisco to London 81 ms 8 years Internet: San Francisco to Sydney 183 ms 20 years TCP packet retransmit 1–3 s 100–300 years OS virtualisation system reboot 4 s 400 years SCSI command time-out 30 s 3 millenia Hardware virtualisation system reboot 40 s 4 millenia Physical system reboot 2 min 12 millenia
25. Event Latency Scaled 1 CPU cycle (3.7 MHz) 0.3 ns 1 s Level 1 cache access 1 ns 3 s Level 2 cache access 3 ns 9 s Level 3 cache access 12 ns 36 s Main memory access (SDRAM) 120 ns 6 min SSD I/O 50–150 µs 2–6 days HDD I/O 1–10 ms 1–12 months Internet: San Francisco to New York 40 ms 4 years Internet: San Francisco to London 81 ms 8 years Internet: San Francisco to Sydney 183 ms 20 years TCP packet retransmit 1–3 s 100–300 years OS virtualisation system reboot 4 s 400 years SCSI command time-out 30 s 3 millenia Hardware virtualisation system reboot 40 s 4 millenia Physical system reboot 2 min 12 millenia
26. Event Latency Scaled 1 CPU cycle (3.7 MHz) 0.3 ns 1 s Level 1 cache access 1 ns 3 s Level 2 cache access 3 ns 9 s Level 3 cache access 12 ns 36 s Main memory access (SDRAM) 120 ns 6 min SSD I/O 50–150 µs 2–6 days HDD I/O 1–10 ms 1–12 months Internet: San Francisco to New York 40 ms 4 years Internet: San Francisco to London 81 ms 8 years Internet: San Francisco to Sydney 183 ms 20 years TCP packet retransmit 1–3 s 100–300 years OS virtualisation system reboot 4 s 400 years SCSI command time-out 30 s 3 millenia Hardware virtualisation system reboot 40 s 4 millenia Physical system reboot 2 min 12 millenia
29. MONOLITH DISTRIBUTED
30. Throughput Load
31. Throughput Load Monolith
32. Throughput Load Monolith
33. Throughput Load Monolith
34. Marc Gravell (2011). Assault by GC. https://blog.marcgravell.com/2011/10/assault-by-gc.html
35. .NET Gen 2 garbage collection Stop the world • Millisecond to second range • Years or decades
36. Throughput Load Monolith
37. Throughput Load Monolith Distributed monolith
38. Throughput Load Monolith Distributed monolith
39. Throughput Load Monolith Distributed monolith
40. The first rule of distributed systems is don’t distribute your system.
41. The first rule of distributed systems is don’t distribute your system.
42. The first rule of distributed systems is don’t distribute your system. …until you have an observable reason to do so.
43. 1. Distributing everything Five common mistakes with distributed systems
44. MONOLITH DISTRIBUTED
45. Functionality Time
46. Functionality Time Monolith
 (Distributed or not)
47. Functionality Time Monolith
 (Distributed or not)
48. Functionality Time Monolith
 (Distributed or not)
49. Functionality Time Monolith
 (Distributed or not)
50. Functionality Time Monolith
 (Distributed or not)
51. Functionality Time Monolith
 (Distributed or not)
52. Functionality Time Monolith
 (Distributed or not) Rewrite
53. Functionality Time Monolith
 (Distributed or not) Rewrite
54. Functionality Time Monolith
 (Distributed or not) Rewrite
55. Functionality Time Monolith
 (Distributed or not) Rewrite
56. Distributed monolith Rewrite
57. Distributed monolith Rewrite
58. Distributed monolith Rewrite Integration layer
59. Distributed monolith Rewrite Integration layer
60. Distributed monolith Rewrite Integration layer Distributed monolith
61. 1. Distributing everything 2. Re-writing everything Five common mistakes with distributed systems
62. Shipping Billing Ordering Inventory
63. Shipping Billing Ordering Inventory
64. Shipping Billing Ordering Inventory
65. Shipping Billing Ordering Inventory
66. Shipping Billing Ordering Inventory
67. Shipping Billing Ordering Inventory
68. Shipping Billing Ordering Inventory
69. Shipping Billing Ordering Inventory
70. Shipping Billing Ordering Inventory
71. Shipping Billing Ordering Inventory
72. Shipping Billing Ordering Inventory
73. Shipping Billing Ordering Inventory
74. Shipping Billing Ordering Inventory
75. Shipping Billing Ordering Inventory
76. Shipping Billing Ordering Inventory
77. Shipping Billing Ordering Inventory
78. Shipping Billing Ordering Inventory
79. Shipping Billing Ordering Inventory
80. Shipping Billing Ordering Inventory
81. Shipping Billing Ordering Inventory Queue
82. Shipping Billing Ordering Inventory Queue
83. Shipping Billing Ordering Inventory Queue
84. Shipping Billing Ordering Inventory Queue 200 OK
 (immediately!)
85. Shipping Billing Ordering Inventory Queue 200 OK
 (immediately!)
86. Shipping Billing Ordering Inventory Queue 200 OK
 (immediately!)
87. Shipping Billing Ordering Inventory Queue 200 OK
 (immediately!)
88. Shipping Billing Ordering Inventory Queue 200 OK
 (immediately!)
89. Shipping Billing Ordering Inventory Queue 200 OK
 (immediately!)
90. Shipping Billing Ordering Inventory Queue 200 OK
 (immediately!)
91. Shipping Billing Ordering Inventory Queue 200 OK
 (immediately!)
92. Shipping Billing Ordering Inventory Queue 200 OK
 (immediately!)
93. Shipping Billing Ordering Inventory Queue 200 OK
 (immediately!)
94. Shipping Billing Ordering Inventory Queue Sorry… 200 OK
 (immediately!)
95. Ordering Shipping Billing Inventory Queue 200 OK
 (immediately!)
96. Ordering Shipping Billing Inventory Queue 200 OK
 (immediately!)
97. Ordering Shipping Billing Inventory Queue 200 OK
 (immediately!)
98. Ordering Shipping Billing Inventory Queue 200 OK
 (immediately!)
99. Ordering Shipping Billing Inventory Queue 200 OK
 (immediately!)
100. Ordering Shipping Billing Inventory Queue 200 OK
 (immediately!)
101. Ordering Shipping Billing Inventory Queue 200 OK
 (immediately!)
102. Ordering Shipping Billing Inventory Queue 200 OK
 (immediately!)
103. Ordering Shipping Billing Inventory Queue 200 OK
 (immediately!)
104. Ordering Shipping Billing Inventory Queue 200 OK
 (immediately!)
105. Ordering Shipping Billing Inventory Queue 200 OK
 (immediately!)
106. Ordering Shipping Billing Inventory Queue 200 OK
 (immediately!)
107. Ordering Shipping Billing Inventory Queue 200 OK
 (immediately!)
108. Ordering Shipping Billing Inventory Queue Sorry… 200 OK
 (immediately!)
109. RabbitMQ Delayed messages Queue Ordering Ordering
110. RabbitMQ Delayed messages Queue Ordering Ordering
111. RabbitMQ Delayed messages Queue Ordering Ordering
112. RabbitMQ Delayed messages Queue Ordering Ordering Queue TTL 6 h Ordering Ordering Queue (Time to live)
113. RabbitMQ Delayed messages Queue Ordering Ordering Queue TTL 6 h Ordering Ordering Queue (Time to live)
114. RabbitMQ Delayed messages Queue Ordering Ordering Queue TTL 6 h Ordering Ordering Queue (Time to live)
115. RabbitMQ Delayed messages Queue Ordering Ordering Queue TTL 6 h Ordering Ordering Queue (Time to live)
116. RabbitMQ Delayed messages Queue Ordering Ordering Queue TTL 6 h Ordering Ordering Queue (Time to live)
117. RabbitMQ Delayed messages Ordering Ordering
118. RabbitMQ Delayed messages Ordering Ordering Queue TTL 15 s Queue
119. RabbitMQ Delayed messages Ordering Ordering Queue TTL 30 s Queue TTL 15 s Queue
120. RabbitMQ Delayed messages Ordering Ordering Queue TTL 60 s Queue TTL 30 s Queue TTL 15 s Queue
121. RabbitMQ Delayed messages Ordering Ordering Queue TTL 120 s Queue TTL 60 s Queue TTL 30 s Queue TTL 15 s Queue
122. RabbitMQ Delayed messages
123. RabbitMQ Delayed messages
124. RabbitMQ Delayed messages
125. RabbitMQ Delayed messages 42 seconds
126. RabbitMQ Delayed messages 4210 seconds
127. RabbitMQ Delayed messages 4210 seconds 1010102 seconds
128. RabbitMQ Delayed messages Queue TTL 32 s Queue TTL 16 s Queue TTL 8 s Queue TTL 4 s Queue TTL 2 s Queue TTL 1 s
129. RabbitMQ Delayed messages Queue TTL 32 s Queue TTL 16 s Queue TTL 8 s Queue TTL 4 s Queue TTL 2 s Queue TTL 1 s 1 0 1 0 1 0
130. RabbitMQ Delayed messages Queue TTL 32 s Queue TTL 16 s Queue TTL 8 s Queue TTL 4 s Queue TTL 2 s Queue TTL 1 s 1 0 1 0 1 0
131. RabbitMQ Delayed messages Queue TTL 32 s Queue TTL 16 s Queue TTL 8 s Queue TTL 4 s Queue TTL 2 s Queue TTL 1 s 1 0 1 0 1 0
132. RabbitMQ Delayed messages Queue TTL 32 s Queue TTL 16 s Queue TTL 8 s Queue TTL 4 s Queue TTL 2 s Queue TTL 1 s 1 0 1 0 1 0
133. RabbitMQ Delayed messages Queue TTL 32 s Queue TTL 16 s Queue TTL 8 s Queue TTL 4 s Queue TTL 2 s Queue TTL 1 s 1 0 1 0 1 0
134. RabbitMQ Delayed messages Queue TTL 32 s Queue TTL 16 s Queue TTL 8 s Queue TTL 4 s Queue TTL 2 s Queue TTL 1 s 1 0 1 0 1 0 4210 seconds
135. RabbitMQ Delayed messages
136. RabbitMQ Delayed messages 28 queues
137. RabbitMQ Delayed messages 28 queues 228 seconds
138. RabbitMQ Delayed messages 28 queues 228 seconds 268,435,456 seconds
139. RabbitMQ Delayed messages 28 queues 228 seconds 268,435,456 seconds 8.5 years
140. go.particular.net/dotnet-day-ch-future
141. Ordering Shipping Billing Inventory Queue Sorry… 200 OK
 (immediately!)
142. Ordering Shipping Billing Inventory Queue Sorry… 200 OK
 (immediately!) Service Bus
143. 1. Distributing everything 2. Re-writing everything 3. Building a service bus Five common mistakes with distributed systems
145. BIG BALL OF MUD
154. BIG BALL OF MUD DISTRIBUTED
155. Customer service ID First name Last name Status Product service ID Name Description Price
156. Customer service ID First name Last name Status Product service ID Name Description Price ? Customer fi rst name Customer last name
157. Customer service ID First name Last name Status Product service ID Name Description Price ? Customer fi rst name Customer last name ? Customer status Product price
158. Customer service ID First name Last name Status Product service ID Name Description Price ? Customer fi rst name Customer last name ? Customer status Product price ? Product name Product description
159. Customer service ID First name Last name Status Product service ID Name Description Price ? Customer fi rst name Customer last name ? Customer status Product price ? Product name Product description
160. Customer service ID First name Last name Status Product service ID Name Description Price ? Customer fi rst name Customer last name ? Customer status Product price ? Product name Product description Customer ID
161. Customer service ID First name Last name Status Product service ID Name Description Price ? Customer fi rst name Customer last name ? Customer status Product price ? Product name Product description Customer ID Customer ID
162. Customer service ID First name Last name Status Product service ID Name Description Price ? Customer fi rst name Customer last name ? Customer status Product price ? Product name Product description Customer ID Customer ID
163. Customer service ID First name Last name Status Product service ID Name Description Price ? Customer fi rst name Customer last name ? Customer status Product price ? Product name Product description Customer ID Customer ID Product ID
164. Customer service ID First name Last name Status Product service ID Name Description Price ? Customer fi rst name Customer last name ? Customer status Product price ? Product name Product description Customer ID Customer ID Product ID Product ID
165. Customer service ID First name Last name Status Product service ID Name Description Price ? Customer fi rst name Customer last name ? Customer status Product price ? Product name Product description Customer ID Customer ID Product ID Product ID
166. go.particular.net/dotnet-day-ch-nouns
167. 1. Distributing everything 2. Re-writing everything 3. Building a service bus 4. De fi ning services as nouns Five common mistakes with distributed systems
168. Shipping Billing Ordering Inventory Queue
169. Shipping Billing Ordering Inventory Queue 200 OK
 (immediately!)
170. Shipping Billing Ordering Inventory Queue 200 OK
 (immediately!) No stock!
171. Shipping Billing Ordering Inventory Queue 200 OK
 (immediately!) No stock!
172. Shipping Billing Ordering Inventory Queue 200 OK
 (immediately!)
173. Shipping Billing Ordering Inventory Queue 200 OK
 (immediately!)
174. Shipping Billing Ordering Inventory Queue 200 OK
 (immediately!)
175. Shipping Billing Ordering Inventory Queue 200 OK
 (immediately!)
176. Shipping Billing Ordering Inventory Queue
177. Shipping Billing Ordering Inventory Queue
178. Shipping Billing Ordering Inventory Queue
179. Shipping Billing Ordering Inventory Queue Timeout!
180. Shipping Billing Ordering Inventory
181. Shipping Billing Ordering Inventory Queue 200 OK
 (immediately!)
182. Shipping Billing Ordering Inventory Queue 200 OK
 (immediately!)
183. 1. Distributing everything 2. Re-writing everything 3. Building a service bus 4. De fi ning services as nouns 5. Striving for consistency Five common mistakes with distributed systems
184. 1. Distributing everything 2. Re-writing everything 3. Building a service bus 4. De fi ning services as nouns 5. Striving for consistency Five common mistakes with distributed systems
185. Adam Ralph Five common mistakes with distributed systems I’ve made them all! particular.net/events
186. Shipping Billing Ordering Inventory 200 OK
 (immediately!) Queue
187. Website Billing Ordering Queue
188. Website Billing Ordering Queue A B C Z X Y
189. Website Billing Ordering Queue CC validator A B C Z X Y
190. Website Billing Ordering Queue CC validator A B C Z X Y
191. Website Billing Ordering Queue CC validator A B C Z X Y HTTP
192. Website Billing Ordering Queue CC validator A B C Z X Y HTTP
193. Website Billing Ordering Queue CC validator A B C Z X Y HTTP A B C Z X Y
194. Website Billing Ordering Queue CC validator A B C Z X Y HTTP A B C Z X Y D
195. Website Billing Ordering Queue CC validator A B C Z X Y HTTP A B C Z X Y D
196. Website Billing Ordering 200 OK
 (after CC Validation) Queue CC validator A B C Z X Y HTTP A B C Z X Y D
197. Website Billing Ordering 200 OK
 (after CC Validation) Queue CC validator A B C Z X Y HTTP A B C Z X Y D
198. Website Billing Ordering 200 OK
 (after CC Validation) Queue CC validator A B C Z X Y HTTP A B C Z X Y D
199. Website Billing Ordering 200 OK
 (after CC Validation) Queue CC validator A B C Z X Y HTTP A B C Z X Y D
200. Website Billing Ordering 200 OK
 (after CC Validation) Queue CC validator A B C Z X Y HTTP A B C Z X Y D
201. Website Billing Ordering 200 OK
 (after CC Validation) Queue CC validator A B C Z X Y HTTP A B C Z X Y D
202. Website Billing Ordering 200 OK
 (after CC Validation) Queue CC validator A B C Z X Y HTTP A B C Z X Y D
203. Website Billing Ordering 200 OK
 (after CC Validation) Queue CC validator A B C Z X Y HTTP A B C Z X Y D
204. https://go.particular.net/dotnet-day-ch-ui
205. 1. Distributing everything 2. Re-writing everything 3. Building a service bus 4. De fi ning services as nouns 5. Striving for consistency Five common mistakes with distributed systems 6. (Bonus!) Conflating service boundaries (logical) with deployment boundaries (physical) Six!
206. 1. Distributing everything 2. Re-writing everything 3. Building a service bus 4. De fi ning services as nouns 5. Striving for consistency Five common mistakes with distributed systems 6. (Bonus!) Conflating service boundaries (logical) with deployment boundaries (physical) Six!
207. Adam Ralph Five common mistakes with distributed systems I’ve made them all! Six!