Yesterday we had another meeting of the Architecture Club where we continued reading Database Internals and started reviewing the second part about distributed systems.

Yesterday we had another meeting of the Architecture Club where we continued reading Database Internals and started reviewing the second part about distributed systems. If you missed past episodes, you can read about them here: 1, 2. Yesterday we discussed the first four chapters of the second part:

— Chapter 8. Introduction & Overview — Chapter 9. Failure Detection — Chapter 10. Leader Election — Chapter 11. Replication and Consistency

At the meeting, we discussed these topics from the point of view of implementing these points within different databases.

Cassandra is the author’s point of view as Cassandra contributors and implicitly looks at many topics from the perspective of a person who agrees with weaker guarantees of consistency than in relational databases. Postgres – Kosti Evteev’s point of view, a guest of this issue, who is an expert in this database and previously led the development of DbaaS in Avito for many years – YDB – from the point of view of this database, our other guest, Oleg Bondar, who is the CPO of Yandex Database and is responsible for the development of this newSQL database, which can be consistent and scale as a NoSQL solution, looked at the book.

More in the article https://apolomodov.medium.com/code-of-architecture-database-internals-part3-788480601498

#ExternalReview #Databases #SystemDesign #SoftwareArchitecture #Software #ComputerScience