delos · shipping · also Delos virtual consensus

Delos

Delos is a replicated-database platform that separates shared-log reconfiguration from pluggable ordering protocols and composes application services from log-structured engines.

VirtualLog maps successive address ranges to Loglets. Changing the active Loglet requires sealing it, reading its tail and conditionally updating the versioned MetaStore mapping. The MetaStore still needs fault-tolerant consensus; virtualization relocates that responsibility rather than eliminating it. [1]

A successful seal prevents new appends from being acknowledged, not all subsequent physical writes. Repair can make unacknowledged entries durable and advance a sealed Loglet's tail. Fixed segment bounds keep those extra entries outside the VirtualLog. [1]

The 2021 design adds stackable engines above the shared log. BaseEngine applies an entry and advances its playback cursor in the same LocalStore transaction. LocalStore flushing can lag the durable shared log; replay restores that materialized state. A successful sync supplies a linearizable read snapshot, not merely a cached local read. [2]

Exception handling depends on determinism. An expected deterministic application exception can roll back its nested work while lower engines retain progress. A non-deterministic storage exception, such as running out of space on one replica, requires stopping that replica to avoid divergent state. [2]

Log reclamation combines constraints: each engine forwards the minimum of its own safe prefix and the upstream limit. Durable playback, completed log backup and snapshot-backup progress can each delay trimming. Installing a new engine uses a rolling deployment followed by a logged activation command, so replicas begin changing state at a consistent position. The paper does not provide native sharding or cross-shard transactions. [2]

Relations

related
CORFU, Tango, Raft

Limitations

  • NativeLoglet needs its sequencer for appends, while seal and checkTail remain available with a responding majority. StripedLoglet waits for preceding positions across all stripes before acknowledging an append; one failed stripe can therefore stop the composed log. The 2020 design virtualizes total ordering, not arbitrary partially ordered protocols. [1]

Citations

  1. Balakrishnan et al. Virtual Consensus in Delos. OSDI 2020, pp. 617-632; sections 3.2-3.4 and 4.2. (accessed 2026-11-16)
  2. Balakrishnan et al. Log-structured Protocols in Delos. SOSP 2021; sections 3.1-3.4 and 4.1-4.2. DOI: 10.1145/3477132.3483544. (accessed 2026-11-16)
Sources & caveats
  • Source-based synthesis of the 2020 and 2021 designs, not a benchmark replication or failure-injection experiment.
  • The shipping classification records the papers' production deployment reports; it does not verify the platform's current deployment or availability to external users.

JSON: /data/terms/delos.json

Published by Hesela team · Updated

Report a correction · Editorial standards · Reuse guidance

Cite this page
Hesela team. Delos. Hesela. 2026-11-16. https://hesela.dev/terms/delos/