Auto saved by Logseq
This commit is contained in:
parent
a22ac90a03
commit
0e11daeee4
|
@ -1163,7 +1163,7 @@
|
|||
where Ramesh is present. If during the update we miss any single row,
|
||||
then there will be two addresses of Ramesh, which will lead to
|
||||
inconsistent and wrong databases.
|
||||
- LATER Block 4
|
||||
- DONE Block 4
|
||||
- DONE Distributed DBMS
|
||||
- DONE client server arch #flashcard
|
||||
id:: 648974ba-9c11-4816-9d5e-0623dc4d4d45
|
||||
|
@ -1286,7 +1286,19 @@
|
|||
3. Partition Tolerance → A query must have an answer, even if the system
|
||||
is partitioned (unless there is a global failure).
|
||||
- BASE: #flashcard
|
||||
-
|
||||
- **Basically Available:**
|
||||
Instead of making it compulsory for immediate consistency,
|
||||
BASE-modelled NoSQL databases will ensure the availability of data by
|
||||
spreading and replicating it across the nodes of the database cluster.
|
||||
- **Soft State:**
|
||||
Due to the lack of immediate consistency, the data values may change
|
||||
over time. The BASE model breaks off with the concept of a database that
|
||||
obligates its own consistency, delegating that responsibility to
|
||||
developers.
|
||||
- **Eventually Consistent**:
|
||||
The fact that BASE does not obligates immediate consistency but it does
|
||||
not mean that it never achieves it. However, until it does, the data
|
||||
reads are still possible (even though they might not reflect reality).
|
||||
- DONE Terms in: [chatGPT](https://chat.openai.com/c/db2ea8df-3bd0-4404-98ae-266afdd8fec1)
|
||||
- LATER Exercises
|
||||
- DONE past year exercise 1
|
||||
|
|
Loading…
Reference in a new issue