Last Monday, we hosted Code of Architecture’s seventh stream of Distributed Systems, where we discussed consistency and replication.
Last Monday, we hosted Code of Architecture's seventh stream of the book.Distributed SystemsIn which we discussed consistency and replication. After graduation, I managed to perform at Teamlead Conf, go to the ballet in Bolshoi, drive to St. Petersburg to perform at St. Petersburg State University and collapse on Friday after working with temperature. 38.5. A couple of days passed like a fog, and only in the evening on Monday I was so smitten as to finish a brief sammari on the seventh issue and put it out.
Let me remind you that we talked together with Vitaly Kondratov, who is cool in distributed systems, and talked about topics. Why is replication necessary and what problems it solves (performance and reliability)And what does it bring with it? (complexity of maintaining consistency) What consistency models are available: data-centric and customer-centric What are data-centric consistency models? (sequential, causal, eventual, continuous) What are client-centric consistency models? (monotonic reads, monotonic writes, read your writes, writes follow reads)Let’s look at the example of ZooKeeper. - How to manage lines (replica management) - What kind of cosistance protocols are there Finally, let’s look at how caching and replication work on the modern Web.
Artifacts from this stream are available at the link n
#SoftwareArchitecture #DistributedSystems #Architecture #SystemDesign #Software #CoA