From 7baf7c91c53c0d75aba701c8256bc26909353b02 Mon Sep 17 00:00:00 2001 From: Rishabh Jain Date: Tue, 3 Aug 2021 11:20:31 -0700 Subject: [PATCH] Update designing-data-intensive-applications.md The books uses object translation as a problem in relational models which the Json model solves. Simply using the word "data" is confusing. --- books/designing-data-intensive-applications.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/books/designing-data-intensive-applications.md b/books/designing-data-intensive-applications.md index ca34231..17441a0 100644 --- a/books/designing-data-intensive-applications.md +++ b/books/designing-data-intensive-applications.md @@ -213,7 +213,7 @@ _Not Only SQL_ has a few driving forces: * Specialised query optimisations * Desire for a more dynamic and expressive data model -**With a SQL model, if data is stored in a relational tables, an awkward translation layer is translated, this is called _impedance mismatch_.** +**With a SQL model, if objects are stored in a relational tables, an awkward translation layer is required, this is called _impedance mismatch_.** JSON model reduces the impedance mismatch and the lack of schema is often cited as an advantage.