# data[].attributes.body
Bounding Numerical Deviation
-Number of unseen updates, the absolute numerical value, or the relative numerical value.

Bounding Ordering Deviation
-For each server keeps a queue of tentative, uncommitted writes

Bounding Staleness Deviation
-Each server maintain a vector clock when receiving server sees that its vector clock is falling behind the sender.

# data[].attributes.body
-  The number of unseen updates, the absolute numerical value, or the relative numerical value. Every server i tracks every other server j’s state about i’s local writes, i.e., the number of i’s local writes not been seen by j. The total number of unseen updates to a server shall never exceed a threshold.

Bounding Staleless Dev
-  Each server maintains a clock T(i), meaning that this server has seen all writes of i up to time T(i).
Let T be the local time. If server i notices that T-T(j) exceeds a threshold, it will pull the writes from server j.

Bounding Ordering Dev
-  Each server keeps a queue of tentative, uncommitted writes. If the length of this queue exceeds a threshold, the server will stop accepting new writes.

irfatiha

# data[].attributes.body
Deviation - is about the differences of the value from one particular point to another

Bounding Ordering Deviations -
Replica server tentatively applies updates that have been submitted to it... and each server will have a local queue of tentative writes(order yet TBD)

Bounding Numerical Deviations-
()
A server pushes a series of write commands to its nearest neighbors (epidemic protocol)... If a receiving server senses that it is not keeping pace with its updates, it asks the sender to push its current state

Bounding Staleness Deviation -
(TIMESTAMP)
Every server keeps a vector clock... When a receiving server sees that its vector clock is falling behind the sender's, it pulls the most recent update

1. one approach->> timestamp each submitted write by its origin server

# data[].attributes.body
ld, it will pull the writes from server j

# data[].attributes.body
Deviation - a measure of difference between the observed value of a variable and some other value, which is that variable's mean.

Bounding Numerical Deviation
The number of unseen updates, the absolute numerical value, or the relative numerical value

Bounding Staleness Deviation
The validity of the oldest write by bounding the difference between the current time and the time of oldest writeon a conit not seen locally.
Bounding ordering deviation
Each server keeps a queue of tentative, uncommited writes. If the length of this queue exceeds a treshold, the server will stop accepting new writes.

# data[].attributes.body
Akmal
Deviation - is about the differences of the value from one particular point to another

Bounding Ordering Deviations - 
Replica server tentatively applies updates that have been submitted to it... and each server will have a local queue of tentative writes(order yet TBD)

Bounding Numerical Deviations- A server pushes a series of write commands to its nearest neighbors (epidemic protocol)... If a receiving server senses that it is not keeping pace with its updates, it asks the sender to push its current state

Bounding Staleness Deviation -
Every server keeps a vector clock... When a receiving server sees that its vector clock is falling behind the sender's, it pulls the most recent update
one approach->> timestamp each submitted write by its origin server



ld, it will pull the writ
ld, it will pull the writes from server j

more_vert
Naim
Naim
Deviation - a measure of difference between the observed value of a variable and some other value, which is that variable's mean.

Bounding Numerical Deviation
The number of unseen updates, the absolute numerical value, or the relative numerical value

Bounding staleness deviation

Amirah Dzuliyana 198126
Amirah 

# data[].attributes.body
Bounding Numerical Deviation
The number of updates that apply to the replica

Bounding Ordering Deviation
Updates may not been committed due to ordering constraints

Bounding Staleness Deviation
The last time a replica was updated more than 1 hour old

# data[].attributes.body
Bounding numberical deviation
-the number of changes, and relative numberical value
Bounding Staleness Deviation
-it about the time related to the replica is still consider to be consistent.
Bounding odering deviation
-it about
mel

# data[].attributes.body
Bounding Numerical Deviation
-  The number of unseen updates, the absolute numerical value, or the relative numerical value. For example,  the value of a local copy of x will never deviate from the real value of x by a threshold.

Bounding Ordering Deviation

-  Each server keeps a queue of tentative, uncommitted writes.  If the length of this queue exceeds a threshold,  the server will stop accepting new writes.

Bounding Staleness Dev

-  Each server maintains a clock T(i), meaning that this server has seen all writes of i up to time T(i).

# data[].attributes.body
Bounding numerical deviation:
the difference between the conit value and relative value of last update.

Bounding staleness deviations:
related to the last time a replica was updated

Bounding ordering deviation:
enforcing globally consistent ordering of tentative writes with primary-based or quorum-based protocols
-khaliq

# data[].attributes.body
Deviation Definition: Measurement of differences between 2 values (time, queue in the buffer, etc.)

Bounding Numerical Dev: Refers to the value by which replicas maybe different. A solution for keeping the numerical deviation within bounds.

Staleness Dev: Refers to the time by which a replica is still considered to be consistent. Relate to the last time a replica was updated. Eg: used in web caches

Ordering Dev: Refers to the maximum number of tentative writes that may be outstanding without having synchronized with other replica servers.

# data[].attributes.body
Bounding Numerical Deviation: A solution for keeping the numerical deviation within the bounds and concentrate on writes to a single data item x.

Bounding Staleness Deviation: Way to keep the staleness of replicas within specified bounds. For example, one approach like timestamp each submitted write by its origin server.

Bounding Ordering Deviation: Replica server tentatively applies updates that have been submitted to it. The ordering deviation is bounded by specifying the maximal length of the queue of tentatives writes.

# data[].attributes.body
-Bounding Numerical Deviation
The number of changes that were not available, the actual numerical value, or the relative numerical value.

-Bounding Staleness Deviation
Every server keeps a vector clock, so when a receiving server sees that its vector is failing behind the sender, it pulls the most recent update

-Bounding  Ordering Deviation
Each server has a local queue  of tentative writes
Ordering deviation is bounded by specifying maximal length of tentative writes queue
Enforce a globally consistent ordering of tentative writes using primary based or quorum based  protocol

ameer

# data[].attributes.headline
Bounding ordering deviation, bounding numerical deviation, bounding staleness deviation - 

# data[].attributes.subject
Bounding ordering deviation, bounding numerical deviation, bounding staleness deviation - 

# data[].attributes.body
Bounding ordering:
- Deviation with respect to the ordering of update operations. Maximum number of uncertain writing that replica servers update when it received it. A specified maximal length of queue is used to bound the ordering deviation.

Boundering numerical:
- Deviation in the numerical values between replica servers. Mostly focusing on keeping the numerical deviation within the fixed value and emphasize on writing to 1 item instead.

Bounding staleness:
- Deviation in the staleness(refers to age or timestamp of update) between replicas to ensure each replicas are consistent.

Adham (Syafiq)

# data[].attributes.body
Deviation - the amount by which a single measurement differs from a fixed value such as the mean.

Bounding Numerical Deviation-
The number of changes that were not available, the actual numerical value, or the relative numerical value.

Staleness Dev - Refers to the time by which a replica is still considered to be consistent. Relate to the last time a replica was updated.

Bounding Ordering Dev
- Ordering deviation is the discrepancy between the local order of writes in a replica and their relative ordering in the eventual final image

Nazri

# data[].attributes.body
bounding numerical
- follows push approach by letting server keep replicas up to date by forwarding writes

bounding staleness
- follows pull approach by letting replicas pull in updates from server

bounding ordering
- replicas tentatively apply updates that have been submitted to it

# data[].attributes.body
Deviation
-It is a measure of the difference between a variable's measured

value and other value, also the mean value of that variable.

1.Bounding Numerical Deviation
The number of changes that were not available, the actual numerical value, or the relative numerical value.

2.Bounding Staleness Deviation
A clock T(i) is maintained by each server, which means that this server has seen everything I writes up to T time T (i)

3.Bounding Ordering Deviation
Each server maintains a preliminary, uncommitted writing queue

-vinasar

# data[].attributes.body
Deviation -  a measure of difference between the observed value of a variable and some other value, often that variable's mean

Bounding Numerical Dev (Value)-
based on the number of unseen updates, the absolute numerical value, or
the relative numerical value

Bounding Ordering Dev (Queue) -
based on queue of tentative, uncommitted writes

Bounding Staleness Dev (Time) -
based on the

Each server maintains a clock T(i), meaning that this server has
seen all writes of i up to time T(i)

-

# data[].attributes.headline
Bounding numerical deviation– The number of unseen updates, the absolute numerical value, or the relative numerical value

# data[].attributes.subject
Bounding numerical deviation– The number of unseen updates, the absolute numerical value, or the relative numerical value

# data[].attributes.body
Bounding staleness deviation
– Each server maintains a clock T(i), meaning that this server has
seen all writes of i up to time T(i)

Bounding ordering deviation
– Each server keeps a queue of tentative, uncommitted writes

Deviation Definition:
Deviation is a measure of difference between the observed value of a variable and  variable's mean. - megat

# data[].attributes.body
Bounding Numerical Dev
-   The value of local copy  never exceed the threshold of real value

Bounding Ordering Dev
- The queue of uncommitted writes will be kept by the server.
- The server stop accepting new write when the length of the queue is exceeds threshold.

Bounding Staleness Dev
- The server will see all writes up to the expected time or clock.
- If primary server has notices that the local time has exceed the threshold , it will pull the writes back.

# data[].attributes.body
Deviation: the amount by which a single measurement differs from a fixed value such as the mean.

Bounding Numerical Dev
- Numerical deviation bounds the difference between the conit value and relative value of last update. A weight can be assigned to the writes which defines the importance of the writes in a specific application. The total weights of unseen writes for a conit can be defined as a numerical deviation in an application

Bounding Ordering Dev

- Ordering deviation is the discrepancy between the local order of writes in a replica and their relative ordering in the eventual final image

Bounding Staleness Dev

- Staleness deviation defines the validity of the oldest write by bounding the difference between the current time and the time of oldest write on a conit not seen locally. -faris

# data[].attributes.body
Bounding Numeriical Deviation is the number of unseen updates, the absolute numerical value or the relative numerical value. It also can be defined as the number and the values of update.

Bounding Ordering Deviation is about each server keeps a queue od tentative, uncommitted writes. It is also defined as the number of uncommitted updates.

Bounding Staleness Deviation is related to the last time a replica was updated. It is  about each server maintains a clock T(i), which is that this server has seen all writes of i up to T(i).  Let T to be the local time, If server i notices that T-T(j) exceeds a threshold, it will pull the writes from server j.