LoginSign Up
← Back to all sparks
T

Tigris

DEVOPS
Velocity5.0

Tigris keeps publishing its architecture, and the newest post opens up the storage engine itself.

object-storagefoundationdbgeo-replications3-compatibilityegress-costsagent-native
◆Current state
This feed is Tigris's engineering blog, and it alternates between protocol critique and descriptions of how the product answers it. The most recent post opens the internals: how Tigris composes ACID metadata, global placement, caching, replication, and background work on FoundationDB into a multi-region object store. Before it came the Recycle Bin — deletion of objects and buckets on top of immutable storage in an active-active geo-replicated database — plus two posts dissecting SigV4 and presigned URLs, and one on agent-native onboarding through tigris init --agent.
◆Where it's heading
The writing is doing product work. Each protocol post establishes a problem — SigV4's canonicalization and clock skew, presigned URLs as deliberate replay attacks, S3 egress pricing on ClickHouse restores — and positions Tigris behavior as the answer, which makes the blog a migration funnel rather than a changelog. The architecture post is a different move: publishing the FoundationDB composition is a credibility play aimed at buyers who need to believe a newer object store can hold multi-region data.
◆Prediction
Expect the protocol-critique-then-Tigris-answer format to continue, with the egress-cost framing recurring as the clearest paid migration path. Feature announcements will likely stay embedded in essays rather than appearing as release notes.

◆Recent moves

  1. 29d ago

    Building a global object store on FoundationDB

    An architecture explainer on composing ACID metadata, placement, caching, replication and background work over FoundationDB. It announces nothing new, but it is the post that makes the previously described features legible as one system rather than a list.

    View source ↗
  2. 1mo ago

    Extending immutability: deletion without losing data

    Describes a Recycle Bin for objects and buckets built on immutable storage, which is a real capability arriving inside an essay. Restoring deletes in an active-active geo-replicated store is the kind of gap that blocks migrations from S3, so closing it matters more than its framing suggests.

    View source ↗
  3. 1mo ago

    SigV4 authentication is surprisingly complicated

    A walkthrough of SigV4's implementation traps — canonicalization, clock skew, and a cache that cannot hold the key. Educational content that builds the case for a compatible implementation without announcing a change to one.

    View source ↗
  4. 1mo ago

    Humans don't install software themselves anymore, their agents do

    Documents tigris init --agent, an onboarding path whose output is written for a coding agent rather than a human. Treating the agent as the installer is a small surface change with a clear read on who Tigris expects to be adopting it.

    View source ↗
  5. 2mo ago

    The Most Expensive ClickHouse Query Is the Restore

    Positions Tigris as the backup and cold-tier target for self-hosted ClickHouse, trading on S3 egress pricing rather than any new capability. It is the sharpest commercial framing in the feed and uses only features that already exist.

    View source ↗
  6. 2mo ago

    Presigned URLs are technically a security vuln

    Argues presigned URLs are replay attacks issued deliberately, then explains what one grants on Tigris storage. Same template as the SigV4 post: a protocol critique that ends at Tigris behavior, with nothing shipped.

    View source ↗