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
  1. Flaw Tolerance

Terminology

Term
Description
Example

Failure

A component is not following its specifications

Crashing program

Error

Part of the program that can generate a failure.

Bug

Fault

Cause of the error.

Programmer

Failure prevention

Prevent the occurrence of a failure

Not hiring sloppy programmers

Failure tolerance

Built a component that can mask the occurrence of a failure

Each component is developed independently by two programmers

Failure removal

Reduce the presence, number or severity of failures

Firing sloppy programmers

Failure prediction

Estimate the actual presence, future incidence and consequence of failures

Estimate how the HR is hiring the programmers

Models of failure

Types of failure
Description of the server behavior

Crash failure

Stops, but until then it works well

Omission: - on reception - on emission

Does not respond to messages Does not receive new messages Does not send messages

Temporal flaw

Responds out of the specified time window

Failure in response: - in value - on the transition of state

Response is incorrect The response is wrong Deviation from the correct control flux

PreviousDependabilityNextConfidence vs. Security

Last updated 2 years ago