Tigris Data

@TigrisData

Tigris is a globally distributed S3-compatible object storage service that provides low latency anywhere in the world. Now with bucket forking.

San Francisco Bay Area

Tigris Data
@TigrisData
Sep 22
At Tigris we love databases, especially FoundationDB. FoundationDB is that: our foundation. It's the basis for everything we do, even our message queue. Turns out it's pretty great to do data and queueing in the same transaction!
1
Tigris Data
@TigrisData
Sep 15
If our objgit post was so good last time, where's objgit post 2? Today we have an update on the epic saga of Xe reinventing Git storage on top of object storage: making seek-native packfiles. What does this mean? Well, git is complicated. Huddle into this thread!
1
Tigris Data
@TigrisData
Sep 8
"We didn't need a database" is normally the kind of catchy blogpost title that shows up months before "We migrated to Postgres". Our friend JP runs AmpBase, and his control plane sits directly on top of Tigris' object storage without a relational database under it.
1
Tigris Data
@TigrisData
Sep 1
Chicago says an object is deleted. Singapore says it exists. Who's right? FoundationDB uses a variant of Paxos for consensus within a cluster, but versionstamps don't compare across clusters. Since we run so many clusters all over the globe, we invented our own protocol for
1
Tigris Data
@TigrisData
Aug 25
Walgit, from @tobi, is exactly what @martinkl was talking about with the classic line: "the log is the database, and everything else is cache or materialized views." In walgit, the git repository is a write-ahead log in a bucket, and the SoT is the log itself, and the machines
2