From 786559a22662c7dba4974db7a426b9b60425c551 Mon Sep 17 00:00:00 2001 From: Otavio Santana Date: Sat, 29 Apr 2023 08:20:17 +0100 Subject: [PATCH] docs: update introduction api Signed-off-by: Otavio Santana --- spec/src/main/asciidoc/chapters/introduction/introduction.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/spec/src/main/asciidoc/chapters/introduction/introduction.adoc b/spec/src/main/asciidoc/chapters/introduction/introduction.adoc index 494696483..7b9ae14d4 100644 --- a/spec/src/main/asciidoc/chapters/introduction/introduction.adoc +++ b/spec/src/main/asciidoc/chapters/introduction/introduction.adoc @@ -37,7 +37,7 @@ public class Deity { } ---- -Developers need to consider vendor lock-in when choosing a NoSQL database for their application. For example, if there is a need to switch out a database considerations include: the time spent on the change; the learning curve of a new database API; the code that will be lost; the persistence layer that needs to be replaced, etc. Jakarta NoSQL avoids most of these issues through the *Mapping* API. +Developers must consider vendor lock-in and low cognitive load when choosing a NoSQL database for their applications. For example, if there is a need to switch out a database, considerations include the time spent on the change; the learning curve of a new database API; the code that will be lost; the persistence layer that needs to be replaced, etc. Jakarta NoSQL avoids most of these issues through the *Mapping* API. Jakarta NoSQL also provides template classes that apply the *Template Method* design pattern to all database operations.