![[Review] Database Internals: A Deep Dive into How Distributed Data Systems Work (Alex Petrov) Summarized.](https://episodes.castos.com/660078c6833215-59505987/images/2636993/c1a-085k3-7zn7z3g7ixmk-rsjh8d.jpg)
Show Notes
Database Internals: A Deep Dive into How Distributed Data Systems Work (Alex Petrov)
- Amazon USA Store: https://www.amazon.com/dp/1492040347?tag=9natree-20
- Amazon Worldwide Store: https://global.buys.trade/Database-Internals%3A-A-Deep-Dive-into-How-Distributed-Data-Systems-Work-Alex-Petrov.html
- Apple Books: https://books.apple.com/us/audiobook/database-internals-a-deep-dive-into-how-distributed/id1661265544?itsct=books_box_link&itscg=30200&ls=1&at=1001l3bAw&ct=9natree
- eBay: https://www.ebay.com/sch/i.html?_nkw=Database+Internals+A+Deep+Dive+into+How+Distributed+Data+Systems+Work+Alex+Petrov+&mkcid=1&mkrid=711-53200-19255-0&siteid=0&campid=5339060787&customid=9natree&toolid=10001&mkevt=1
- Read more: https://english.9natree.com/read/1492040347/
#Btreeindexing #LSMtreecompaction #Writeaheadlogging #Replicationconsistency #Distributedconsensus #DatabaseInternals
Database Internals: A Deep Dive into How Distributed Data Systems Work is a technical systems book by Alex Petrov, published by O Reilly. It examines the mechanisms beneath database APIs and query languages: how records are laid out on disk, located efficiently, updated safely, replicated across machines, and kept coherent when machines fail. The book is organized around two connected concerns. Its storage-engine material explains the data structures and file-management decisions that shape local database performance and reliability. Its distributed-systems material addresses the additional coordination problems that emerge when data and computation span nodes. Rather than presenting a guide to administering one product, Petrov compares recurring implementation approaches and the trade-offs behind them. B-trees, log-structured merge trees, write-ahead logging, replication, consistency, transactions, failure detection, and consensus are treated as engineering building blocks. The intended reader is a backend or infrastructure engineer who already uses databases and wants a more concrete basis for evaluating performance behavior, operational risks, and architectural choices.
- Amazon USA Store: https://www.amazon.com/dp/1492040347?tag=9natree-20
- Amazon Worldwide Store: https://global.buys.trade/Database-Internals%3A-A-Deep-Dive-into-How-Distributed-Data-Systems-Work-Alex-Petrov.html
- Apple Books: https://books.apple.com/us/audiobook/database-internals-a-deep-dive-into-how-distributed/id1661265544?itsct=books_box_link&itscg=30200&ls=1&at=1001l3bAw&ct=9natree
- eBay: https://www.ebay.com/sch/i.html?_nkw=Database+Internals+A+Deep+Dive+into+How+Distributed+Data+Systems+Work+Alex+Petrov+&mkcid=1&mkrid=711-53200-19255-0&siteid=0&campid=5339060787&customid=9natree&toolid=10001&mkevt=1
- Read more: https://english.9natree.com/read/1492040347/
#Btreeindexing #LSMtreecompaction #Writeaheadlogging #Replicationconsistency #Distributedconsensus #DatabaseInternals
Database Internals: A Deep Dive into How Distributed Data Systems Work is a technical systems book by Alex Petrov, published by O Reilly. It examines the mechanisms beneath database APIs and query languages: how records are laid out on disk, located efficiently, updated safely, replicated across machines, and kept coherent when machines fail. The book is organized around two connected concerns. Its storage-engine material explains the data structures and file-management decisions that shape local database performance and reliability. Its distributed-systems material addresses the additional coordination problems that emerge when data and computation span nodes. Rather than presenting a guide to administering one product, Petrov compares recurring implementation approaches and the trade-offs behind them. B-trees, log-structured merge trees, write-ahead logging, replication, consistency, transactions, failure detection, and consensus are treated as engineering building blocks. The intended reader is a backend or infrastructure engineer who already uses databases and wants a more concrete basis for evaluating performance behavior, operational risks, and architectural choices.
