Fix typo - lobsided -> lopsided (#11)
This commit is contained in:
parent
16651d57d9
commit
aaecc59f6a
@ -844,7 +844,7 @@ Common ways to shard a table of users is either through the user's last name ini
|
||||
##### Disadvantage(s): sharding
|
||||
|
||||
* 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.
|
||||
* Joining data from multiple shards is more complex.
|
||||
* Sharding adds more hardware and additional complexity.
|
||||
|
Loading…
Reference in New Issue
Block a user