![]() ![]() High availability, low latency, occasional stale read.Multi datacenter, offline clients, collaborative editing.Scalability of read-only replicas requires async replication.Two operations are concurrent if neither “happens-before” the other.RPC/location transparency: there is no point to make a remote service look too much like a local object, because it is a fundamentally different thing.Base64 encoding increases data size by 33%.Less convenient for simple one-off queries.Good for evolvability, ease to add new relations and properties.Data models affect how we think about the problem that we are solving.Every legacy system is unpleasant on its own way.Reliability: Systems should work correctly even in the face of adversity, including human error.Martin also explains some of the book contents his distributed system course. It made me smile that there is one chapter dedicated to the perils of distributed programming, when the fact is that the whole book is a warning after another of all the possible things that can go wrong. These are my notes on Designing Data-Intensive Applications by Martin Kleppmann. ![]()
0 Comments
Leave a Reply. |