From 6914cd9160d98a6b4d592a493415ed30ff47ddf3 Mon Sep 17 00:00:00 2001 From: Olaf van der Spek Date: Tue, 18 Jul 2017 04:08:36 +0200 Subject: [PATCH] Fix typo in denormalization section (#95) --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index c60f764..b52157f 100644 --- a/README.md +++ b/README.md @@ -877,7 +877,7 @@ Denormalization attempts to improve read performance at the expense of some writ Once data becomes distributed with techniques such as [federation](#federation) and [sharding](#sharding), managing joins across data centers further increases complexity. Denormalization might circumvent the need for such complex joins. -In most systems, reads can heavily number writes 100:1 or even 1000:1. A read resulting in a complex database join can be very expensive, spending a significant amount of time on disk operations. +In most systems, reads can heavily outnumber writes 100:1 or even 1000:1. A read resulting in a complex database join can be very expensive, spending a significant amount of time on disk operations. ##### Disadvantage(s): denormalization