Globally Distributed Object Storage with Tigris

Summary

Globally distributed object storage is presented as a way to avoid the latency and application complexity that arise when modern apps route uploads and downloads through a single-region S3 bucket. Tigris addresses this with redundant FoundationDB clusters for object tracking, Fly.io NVMe volumes as a first-level raw-byte cache, and a queueing system modeled on Apple’s QuiCK paper that sends data to replicas, in-demand regions, and third-party stores such as S3. Objects smaller than about 128 kilobytes are instantly global by default, while the platform also provides inter-region routing, consistency guarantees, instant purge, and relay regions. Its S3-compatible API means existing S3 libraries can be reused, and fly storage create injects the required AWS configuration and secrets. Fly.io says the partnership delivers object storage under its billing system without requiring a separate account.

Takeaways

1. 1

   Objects smaller than about 128 kilobytes are instantly global by default according to the post.

2. 2

   Tigris is described as globally distributed object storage rather than a CDN, with consistency guarantees, instant purge, inter-region routing, and relay regions.

3. 3

   Existing S3 libraries can use Tigris without code changes, while Fly.io bills the service through the existing Fly.io account.