Engineering blog

How Tigris resolves write conflicts across regions: timestamp-based replication on FoundationDB, clock skew races, and the tradeoffs of each bucket type.

Deleting data is hard in a geo-replicated active-active database. Here's how Tigris built a Recycle Bin for objects and buckets on top of immutable storage.

Tigris puts your objects all over the world, but how do we do it? Today we'll break down the strategies to Tigris' global replication and how it combines fundamental parts of distributed systems to make it happen.

Tigris is a globally available, S3 compatible object storage service. Tigris uses FoundationDB's transactional key-value interface for its underlying metadata storage. In the first post of the series we will share the details of how we have built the metadata layer on top of FoundationDB. We will…

Building secondary indexes for is always about balance. A balance between a system that scales and is easy to manage and an API that is intuitive and delightful for a developer to use. Recently at Tigris Data, we have been adding secondary indexes to our metadata store that runs on top of Founda…

Tigris is a globally available, S3 compatible object storage service that uses FoundationDB for its metadata storage. This blog post describes how we perform backups on FoundationDB, and what options exist for that purpose.

Tigris is a globally available, S3 compatible object storage service. Tigris uses FoundationDB's transactional key-value interface for its underlying metadata storage. In this blog post, we will describe transactions in Tigris, delving into the topics of serializable transactions, the mechanics of t…

Why Tigris leverages FoundationDB for its metadata storage layer