Skip to content

Commit aaecc59

Browse files
Jamstahdonnemartin
authored andcommitted
Fix typo - lobsided -> lopsided (donnemartin#11)
1 parent 16651d5 commit aaecc59

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -844,7 +844,7 @@ Common ways to shard a table of users is either through the user's last name ini
844844
##### Disadvantage(s): sharding
845845

846846
* You'll need to update your application logic to work with shards, which could result in complex SQL queries.
847-
* 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.
847+
* 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.
848848
* 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.
849849
* Joining data from multiple shards is more complex.
850850
* Sharding adds more hardware and additional complexity.

0 commit comments

Comments
 (0)