mirrors
/
system-design-primer
mirror of https://github.com/donnemartin/system-design-primer.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Typo - lobsided -> lopsided

pull/11/head
James Hewitt 2017-03-09 14:21:18 +00:00 committed by GitHub
parent 684679f9a0
commit 6417781b71
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
README.md
View File

@ -844,7 +844,7 @@ Common ways to shard a table of users is either through the user's last name ini
##### Disadvantage(s): sharding ##### Disadvantage(s): sharding
* You'll need to update your application logic to work with shards, which could result in complex SQL queries. * You'll need to update your application logic to work with shards, which could result in complex SQL queries.
* Data distribution can become lobsided in a shard. For example, a set of power users on a shard could result in increased load to that shard compared to others. * Data distribution can become lopsided in a shard. For example, a set of power users on a shard could result in increased load to that shard compared to others.
* Rebalancing adds additional complexity. A sharding function based on [consistent hashing](http://www.paperplanes.de/2011/12/9/the-magic-of-consistent-hashing.html) can reduce the amount of transferred data. * Rebalancing adds additional complexity. A sharding function based on [consistent hashing](http://www.paperplanes.de/2011/12/9/the-magic-of-consistent-hashing.html) can reduce the amount of transferred data.
* Joining data from multiple shards is more complex. * Joining data from multiple shards is more complex.
* Sharding adds more hardware and additional complexity. * Sharding adds more hardware and additional complexity.