Software ArchitectureAtlas

Software Architecture Atlas

Gain an overview. Understand the connections.

Standalone conceptModelChapter II · Distribution · Building block 6 of 11

PACELC

CAP leaves out the everyday trade-off between latency and consistency.

By Michael Meierhoff · Meierhoff Systems

  1. If partitionIf partition: During P, trade off A and C.
  2. ElseElse: Without P, compare latency and consistency.
  3. Operating pointOperating point: Make the decision concrete per access path.

Context

Why this is important

Make latency and consistency visible even without partitions.

Make latency and consistency visible even without partitions.

Shop example · Mapping

PACELC: inspect the decision

The shop example uses the existing shared database and seven modules. Any added service or deployment model is a hypothetical extension. On the shop’s order flow, the cart reads the last replicated product price from a regional replica. The team permits brief replication lag for fast local responses, but requires a coordinated price check at final checkout. During a partition, checkout waits or fails while the catalogue remains readable. PACELC helps discuss these paths separately and set measurable latency and consistency goals.

This is how you read the picture

  1. If partition If partition
  2. Else Else
  3. Operating point Operating point
PACELC: inspect the decision
ConceptMeaningReview question
If partitionDuring P, trade off A and C.Which trade-off applies to price reads during normal operation?
ElseWithout P, compare latency and consistency.What changes before checkout?
Operating pointMake the decision concrete per access path.Which additional situation does PACELC describe?
Das Modell lenkt die Aufmerksamkeit auf die alltäglichen Kosten von Replikation und Koordination. Es fasst Systemverhalten zusammen, ersetzt aber keine Analyse einzelner Lese-/Schreibpfade, Quoren und Fehlerszenarien. Use the questions in the second column to test this scenario.

Benefits & limitations

Helps if:

  • Make latency and consistency visible even without partitions.
  • Examine read and write paths in normal operation and during partitions.

Boundaries

  • PACELC frames trade-offs but proves no property of a specific system.
  • PACELC structures design choices but provides no latency or consistency measurements without measurement.

In practice

  1. Classify partition behavior and normal operation separately for cart display and checkout; identify where availability, latency, and consistency are traded off.
  2. Set the maximum allowed replication lag for the displayed price and distinguish it from the coordinated price validation at authoritative order submission.
  3. Measure latency and replication lag per path and test both partition and normal operation; revise the policy if agreed limits for checkout or display are missed.
Read the detailed explanation

PACELC extends CAP reasoning to normal operation: during a partition (P), A represents availability and C consistency; else (E), the trade-off is between latency (L) and consistency (C).

The model highlights the everyday cost of replication and coordination. It summarizes system behavior but does not replace analysis of individual read/write paths, quorums, and failure scenarios.

The shop example uses the existing shared database and seven modules. Any added service or deployment model is a hypothetical extension. On the shop’s order flow, the cart reads the last replicated product price from a regional replica. The team permits brief replication lag for fast local responses, but requires a coordinated price check at final checkout. During a partition, checkout waits or fails while the catalogue remains readable. PACELC helps discuss these paths separately and set measurable latency and consistency goals. cap and cap theorem help compare this decision with adjacent concerns.

Check your understanding

Test yourself in three stages

  1. ReadingCheck in the picture

    Which trade-off applies to price reads during normal operation?

    View the solution with justification

    Regional latency is prioritized for fast price reads.

  2. ApplyingTransferred to a new situation

    What changes before checkout?

    View the solution with justification

    Price coordination happens centrally before the order becomes final.

  3. EvaluateWeighing an alternative

    Which additional situation does PACELC describe?

    View the solution with justification

    The latency-consistency trade-off during normal operation, even without a partition.

Explore further

These building blocks continue the thoughts of this page.

DistributionCAP & PACELCContext and comparisonOpening DistributionCAP TheoremConceptual connectionOpening DataConsistency modelsConceptual connectionOpening

References

Continue on the learning path

Next in Distributed systems: CAP Theorem.

11 Building blocks

Continue withCAP Theorem