You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Typo "conidering" changed to "considering" (#21165)
Typo "conidering" in the following sentence under "The CAP theorem" section should be changed to "considering":
"> Nowadays, care must be taken when conidering the CAP theorem constraints."
Copy file name to clipboardExpand all lines: docs/architecture/cloud-native/relational-vs-nosql-data.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -60,7 +60,7 @@ This kind of result is known as eventual consistency, a characteristic of distri
60
60
61
61
High availability and massive scalability are often more critical to the business than strong consistency. Developers can implement techniques and patterns such as Sagas, CQRS, and asynchronous messaging to embrace eventual consistency.
62
62
63
-
> Nowadays, care must be taken when conidering the CAP theorem constraints. A new type of database, called NewSQL, has emerged which extends the relational database engine to support both horizontal scalability and the scalable performance of NoSQL systems.
63
+
> Nowadays, care must be taken when considering the CAP theorem constraints. A new type of database, called NewSQL, has emerged which extends the relational database engine to support both horizontal scalability and the scalable performance of NoSQL systems.
64
64
65
65
## Considerations for relational vs. NoSQL systems
0 commit comments