From aaecc59f6a22915ae3b4ce6918e682f9467d5ffb Mon Sep 17 00:00:00 2001 From: James Hewitt Date: Fri, 10 Mar 2017 00:37:39 +0000 Subject: [PATCH] Fix typo - lobsided -> lopsided (#11) --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 809e7be..0a84fe9 100644 --- a/README.md +++ b/README.md @@ -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.