Notes - MIECT
Computação Distribuída
Notes - MIECT
Computação Distribuída
  • Computação Distribuída
  • Introduction / Architecture
    • Distributed Systems
    • Architecture
    • Middleware Organizations
    • Processes
    • Threads
    • Virtualization
    • Clients
    • Servers
    • Migration
  • Communications
    • OSI Model
    • Middleware Layer
    • Types of Communication
    • Remote Call Procedure (RPC)
    • Sockets
    • Application-level Multicasting
  • Naming
    • Names
    • Addresses
    • Identifiers
    • Naming Systems
      • Flat Naming
      • Structured Naming
    • Internet Domain Name System (DNS)
    • Attribute-based naming - LDAP
  • Coordination
    • Clocks
      • Synchronizing without UTC
    • Reference Broadcast Synchronization – RBS
    • Happened-Before Relation
      • Logical Clocks
      • Vector Clocks
    • Mutual Exclusion Algorithms
    • Election Algorithms
    • Distributed Events Correspondance
  • Consistency & Replication
    • Replication
    • Performance and Scalability
    • Client-centric models
    • Replicates
    • Unicasting vs. Multicasting
    • Continuous Consistency
    • Protocols
  • Flaw Tolerance
    • Dependability
    • Terminology
    • Confidence vs. Security
    • Halting failures
    • Redundancy to mask failures
    • Consensus
      • Realistic
      • Consensus in arbitrary failures
      • Achieving failure tolerance
      • Distributed consensus
    • Failure Detection
    • Reliable RPCs
    • Distributed commit protocols
  • Python asyncio & Friends
    • Async
    • Sync vs. Async
    • Tools
  • Flask
    • Introduction
    • Python Requests
  • Containers
    • VM's vs Containers
    • OS Support
    • Building a container
    • Tools
    • Portability
    • Docker
      • Container
  • Map Reduce
    • Map Recude
    • Hadoop
    • Software Architecture
    • Task Scheduling
    • Comparison With Traditional Models
  • Cloud Computing
    • Cloud Computing
    • IaaS – Infrastructure as a Service
    • PaaS – Platform as a Service
    • SaaS – Software as a Service
    • Business Models
Powered by GitBook
On this page
  • Eventual consistency
  • Monotonic readings
  • Monotonic writings
  • Reading after writing
  • Writing after reading
  1. Consistency & Replication

Client-centric models

PreviousPerformance and ScalabilityNextReplicates

Last updated 1 year ago

Eventual consistency

Monotonic readings

If a process reads the value of a given x, any successive reading operation over x by the same process will return the same value or a more recent one.

Monotonic writings

A process writing operation in x is completed before any successive writing operation on x by the same process.

Reading after writing

The effect of a process writing operation over data x will always be seen by the same process following reading operations over x.

Writing after reading

A process's writing operation over x data after a previous reading operation over x by the same process is guaranteed to occur over the same x value.

Monotonic reading
Non-monotonic reading
Monotonic write
Data store does not make consistency available by monotonic writing
Whitout consistency by monotonic writing
Consistent because WS(x1, x3) although x1, aperantly, overides x2
Read after consistent write
Non-consistent
Write after consistent read
Non-consistent