<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/the-atomiclog-logdrive-strong-vs-weak-sealing-jack-vanlightly-lmmcrqcm4" -->

---
title: The AtomicLog + LogDrive: Strong vs weak sealing — Jack...
description: An in-depth exploration of segment sealing within the AtomicLog and LogDrive abstractions from Virtual Consensus research, comparing strong seals (enforced...
canonical: https://daily.dev/posts/the-atomiclog-logdrive-strong-vs-weak-sealing-jack-vanlightly-lmmcrqcm4
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: The AtomicLog + LogDrive: Strong vs weak sealing — Jack Vanlightly | daily.dev
og:description: An in-depth exploration of segment sealing within the AtomicLog and LogDrive abstractions from Virtual Consensus research, comparing strong seals (enforced...
og:url: https://daily.dev/posts/the-atomiclog-logdrive-strong-vs-weak-sealing-jack-vanlightly-lmmcrqcm4
og:image: https://api.daily.dev/og/posts/lMMCrqcm4.png
og:image:alt: The AtomicLog + LogDrive: Strong vs weak sealing — Jack Vanlightly
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# The AtomicLog + LogDrive: Strong vs weak sealing — Jack Vanlightly

**[Jack Vanlightly](https://daily.dev/sources/jack-vanlightly)** · 8 min read · 0 upvotes · 0 comments

## Summary

An in-depth exploration of segment sealing within the AtomicLog and LogDrive abstractions from Virtual Consensus research, comparing strong seals (enforced inline by storage, as in Delos's NativeLoglet or Apache BookKeeper) versus weak seals (an out-of-band register checked post-write, as used in the LogDrive paper). The piece explains how LogDrive's single-value register semantics allow cheaper quorum composition and simpler storage requirements, but require a post-write seal check. It then walks through the added complexity of implementing a strong seal over passive storage (like S3 or DynamoDB) using barrier values, conditional writes, and Paxos-style ballots, concluding with a trade-off framing between portability and acknowledgement latency.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://jack-vanlightly.com/blog/2026/8/28/the-atomiclog-logdrive-strong-vs-weak-sealing>

## Questions this post answers

### What is the difference between a strong seal and a weak seal in a segmented shared log?

A strong seal is enforced inline by the append path itself, so a write fails immediately once sealed, as in Delos's NativeLoglet or Apache BookKeeper. A weak seal lets the write complete normally, with success instead gated by a separate post-write check of an independent seal register, which is the approach used in the LogDrive paper.

_Engineers designing shared-log systems can track deeper explainers on sealing trade-offs like these on daily.dev._

### Why does the LogDrive abstraction only need single-value register semantics instead of write-once or conditional registers?

Single-value semantics suffice because the AtomicLog's sequencer guarantees only one distinct value is ever proposed to a given address, and the sequencer itself is never replaced or recovered; if it fails, the AtomicLog is sealed and the VirtualLog moves to a new one. This avoids the ballot-aware reconciliation Paxos needs after leader changes, letting a QuorumLogDrive write in a single round trip instead of two.

_Developers weighing storage backends for log-based systems can follow reasoning like this on daily.dev when picking primitives._

### How can a strong seal be implemented over passive storage services like S3 or DynamoDB that lack fencing?

A strong seal over passive storage requires conditional writes to install barrier values ahead of the write tail, ensuring no further normal writes can succeed once the barrier is placed. For singleton log drives, write-once-register semantics let whoever writes first win; for quorum log drives, it requires conditional register semantics plus a Paxos-style two-phase protocol using ballot 1+ for barrier entries.

_Anyone architecting log sealing over object storage can dig into consensus trade-offs like these via daily.dev._

## Similar posts on daily.dev

- [The LogDrive: Flexible Composition Through Abstraction in Shared Logs — Jack Vanlightly](https://daily.dev/posts/the-logdrive-flexible-composition-through-abstraction-in-shared-logs-jack-vanlightly-uq9jbhsnw) · Jack Vanlightly · 0 upvotes · 0 comments
- [Speech at PGDay Israel 2026：Durability, Consistency, and Performance](https://daily.dev/posts/speech-at-pgday-israel-2026-durability-consistency-and-performance-yduiljbzp) · Planet PostgreSQL · 0 upvotes · 0 comments
- [Every fast write moves work somewhere else](https://daily.dev/posts/every-fast-write-moves-work-somewhere-else-k4xugsl0j) · Hacker News · 0 upvotes · 0 comments
- [Building a Database on S3](https://daily.dev/posts/building-a-database-on-s3-z6q1mg0wr) · Metadata · 47 upvotes · 0 comments

---

Tags: [#distributed-systems](https://daily.dev/tags/distributed-systems), [#system-design](https://daily.dev/tags/system-design)

[View this post on daily.dev](https://daily.dev/posts/the-atomiclog-logdrive-strong-vs-weak-sealing-jack-vanlightly-lmmcrqcm4)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"The AtomicLog + LogDrive: Strong vs weak sealing — Jack Vanlightly","url":"https://daily.dev/posts/the-atomiclog-logdrive-strong-vs-weak-sealing-jack-vanlightly-lmmcrqcm4","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/the-atomiclog-logdrive-strong-vs-weak-sealing-jack-vanlightly-lmmcrqcm4"},"datePublished":"2026-08-28T12:44:30.599Z","dateModified":"2026-11-01T18:47:32.540Z","description":"An in-depth exploration of segment sealing within the AtomicLog and LogDrive abstractions from Virtual Consensus research, comparing strong seals (enforced...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/fbaec45f36023322f1b7cc98b0db6cb1?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/fbaec45f36023322f1b7cc98b0db6cb1?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Jack Vanlightly","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Jack Vanlightly","logo":"https://media.daily.dev/image/upload/s--lIrxyl_V--/f_auto,q_auto/v1781695531/logos/jack-vanlightly?_a=BAMAMiWQ0","url":"https://daily.dev/sources/jack-vanlightly"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/the-atomiclog-logdrive-strong-vs-weak-sealing-jack-vanlightly-lmmcrqcm4","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"distributed-systems,system-design","timeRequired":"PT8M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Jack Vanlightly","item":"https://daily.dev/sources/jack-vanlightly"},{"@type":"ListItem","position":3,"name":"The AtomicLog + LogDrive: Strong vs weak sealing — Jack Vanlightly"}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/the-atomiclog-logdrive-strong-vs-weak-sealing-jack-vanlightly-lmmcrqcm4#faq","mainEntity":[{"@type":"Question","name":"What is the difference between a strong seal and a weak seal in a segmented shared log?","acceptedAnswer":{"@type":"Answer","text":"A strong seal is enforced inline by the append path itself, so a write fails immediately once sealed, as in Delos's NativeLoglet or Apache BookKeeper. A weak seal lets the write complete normally, with success instead gated by a separate post-write check of an independent seal register, which is the approach used in the LogDrive paper. Engineers designing shared-log systems can track deeper explainers on sealing trade-offs like these on daily.dev."}},{"@type":"Question","name":"Why does the LogDrive abstraction only need single-value register semantics instead of write-once or conditional registers?","acceptedAnswer":{"@type":"Answer","text":"Single-value semantics suffice because the AtomicLog's sequencer guarantees only one distinct value is ever proposed to a given address, and the sequencer itself is never replaced or recovered; if it fails, the AtomicLog is sealed and the VirtualLog moves to a new one. This avoids the ballot-aware reconciliation Paxos needs after leader changes, letting a QuorumLogDrive write in a single round trip instead of two. Developers weighing storage backends for log-based systems can follow reasoning like this on daily.dev when picking primitives."}},{"@type":"Question","name":"How can a strong seal be implemented over passive storage services like S3 or DynamoDB that lack fencing?","acceptedAnswer":{"@type":"Answer","text":"A strong seal over passive storage requires conditional writes to install barrier values ahead of the write tail, ensuring no further normal writes can succeed once the barrier is placed. For singleton log drives, write-once-register semantics let whoever writes first win; for quorum log drives, it requires conditional register semantics plus a Paxos-style two-phase protocol using ballot 1+ for barrier entries. Anyone architecting log sealing over object storage can dig into consensus trade-offs like these via daily.dev."}}]}
```

