jasder
/
school-of-sre
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

More formatting

This commit is contained in:
Sai Kiran Kanuri 2020-11-18 12:59:33 +05:30
parent 55f6275975
commit 4deec2767f
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
courses/databases_nosql/key_concepts.md
View File

@ -34,15 +34,15 @@ NoSQL systems support different levels of eventual consistency models. For examp
* Read Your Own Writes Consistency * Read Your Own Writes Consistency
A client will see his updates immediately after they are written. The reads can hit nodes other than the one where it was written. However he might not see updates by other clients immediately. A client will see his updates immediately after they are written. The reads can hit nodes other than the one where it was written. However he might not see updates by other clients immediately.
* Session Consistency: * Session Consistency:
A client will see the updates to his data within a session scope. This generally indicates that reads & writes occur on the same server. Other clients using the same nodes will receive the same updates. A client will see the updates to his data within a session scope. This generally indicates that reads & writes occur on the same server. Other clients using the same nodes will receive the same updates.
* Casual Consistency * Casual Consistency
A system provides causal consistency if the following condition holds: write operations that are related by potential causality are seen by each process of the system in order. Different processes may observe concurrent writes in different orders A system provides causal consistency if the following condition holds: write operations that are related by potential causality are seen by each process of the system in order. Different processes may observe concurrent writes in different orders