3 ms·
For further reading, Dan Abadi's post at http://dbmsmusings.blogspot.com/2018/09/newsql-database-systems-are-failing-to.html http://dbmsmusings.blogspot.com/201
by evanweaver 8y ago
For further reading, Dan Abadi's post at http://dbmsmusings.blogspot.com/2018/09/newsql-database-systems-are-failing-to.html http://dbmsmusings.blogspot.com/2018/09/newsql-database-syst... addresses the Spanner issues more directly.
I don't think there's a great reference for the Percolator transaction architecture specifically, but there is a brief description here: https://blog.octo.com/en/my-reading-of-percolator-architecture-a-google-search-engine-component/ https://blog.octo.com/en/my-reading-of-percolator-architectu...
One thing I learned recently is that FoundationDB is essentially the Percolator model (timestamp oracle), even though FoundationDB predated the Percolator paper.
- williamallthing 8y agoWhat consistency model does FDB provide?
- evanweaver 8y agoIn my understanding, it can provide strict serializability. The main difference from actual Percolator is that FoundationDB manages range locks through a logically separate pool of in-memory lock caches, instead of writing durable locks to the replicas, but the end result is the same. External consistency for read/write transactions within a single datacenter at a time.
- wwilson 8y agoThere is no correctness limitation on using FoundationDB in multiple datacenters, and if you do most of your writes in a single datacenter while using the others for disaster recovery, the latency is honestly pretty good too (especially with some of the new 6.0 features). EDIT: I was wondering why this conversation was giving me deja vu, and then I remembered that you and Dave discussed this in detail last month: https://news.ycombinator.com/item?id=18258805 https://news.ycombinator.com/item?id=18258805
- evanweaver 8y agoI forgot about that; thanks for the link. I didn't intend to imply a correctness limitation.