https://www.youtube.com/watch?v=TlU1opuCXB0
Custom Java appliance: https://www.azul.com/
At 14 minutes talks about synchronous systems. Like in CircleCI where all notes must finish before and he can move to the next step.
ETTO rate of change versus thoroughness
They require maintenance. You have to constantly be working on your monitoring and automation.
Death Star Adrian.
Best practice his data design
At 33:40 talk-silence-is-golden
talk-hopelessness-and-confidence-distributed-systems#where-data-independent1 At 34 Where is the data needs to coordinate and where it can be independent talk-hopelessness-and-confidence-distributed-systems#where-data-independent1
Build silence into our systems.
One way of doing that would be to have a cache of the remote data. That sounds a little bit like talk-building-scalable-stateful-services
talk-hopelessness-and-confidence-distributed-systems#acceptably-stale-data1 At 36 What is acceptably stale data, so you can reduce communication between systems? talk-hopelessness-and-confidence-distributed-systems#acceptably-stale-data1
At 37, design for the worst case. What if the worst case isn't as bad as you think it is?