From 477972ba9b0eb30f6540bf4c08dff5bdd0785f07 Mon Sep 17 00:00:00 2001 From: wangyunlai Date: Tue, 5 Mar 2024 20:39:46 +0800 Subject: [PATCH] add paper in replication optimization --- README.md | 1 + 1 file changed, 1 insertion(+) diff --git a/README.md b/README.md index ea1532843..a4f9319cc 100644 --- a/README.md +++ b/README.md @@ -402,6 +402,7 @@ An updated and organized reading list for illustrating the patterns of scalable, * [Black-Box Auditing: Verifying End-to-End Replication Integrity between MySQL and Redshift at Yelp](https://engineeringblog.yelp.com/2018/04/black-box-auditing.html) * [Partitioning Main MySQL Database at Airbnb](https://medium.com/airbnb-engineering/how-we-partitioned-airbnb-s-main-database-in-two-weeks-55f7e006ff21) * [Herb: Multi-DC Replication Engine for Schemaless Datastore at Uber](https://eng.uber.com/herb-datacenter-replication/) + * [Low-Overhead Paxos Replication](https://link.springer.com/article/10.1007/s41019-017-0039-z) * [Sharding](https://quabase.sei.cmu.edu/mediawiki/index.php/Shard_data_set_across_multiple_servers_(Range-based)) * [Sharding MySQL at Pinterest](https://medium.com/@Pinterest_Engineering/sharding-pinterest-how-we-scaled-our-mysql-fleet-3f341e96ca6f) * [Sharding MySQL at Twilio](https://www.twilio.com/engineering/2014/06/26/how-we-replaced-our-data-pipeline-with-zero-downtime)