Worth a read: @theprincessxena and @GarrenSmith from @TigrisData write about moving from FoundationDB to Kafka for their message queue.
Also: @raindrop_ai raised a $35M Series A. And @AlphaSenseInc is hiring a Senior Product Security Engineer in the US.
Links in bio
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!
We fixed that by adding Kafka to the stack. Kafka has a...reputation for being a bit grotestue in the infrastructure side of things (the zookeeper can't even pet the animals 😔), but we've found that it means we take write pressure off of FoundationDB so the servers stay up.
Either way if you want to learn more from a detailed writeup by a human with blood, feelings, and hopefully isn't an axe murderer, please take a look at the blogpost!
tigrisdata.com/blog/quick-fd…
Git packfiles assume a local disk, so Xe ended up building a custom packfile format to run git directly on object storage. Worked out pretty well, git push down from 3.5 minutes to 14 seconds.
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!
This ended up making Git object storage on top of Tigris object storage upwards of 4.5-14.6 times faster than the old approach of badly adapting filesystem interfaces to Tigris.
For most products you can build persistence entirely on object storage now. Conditional writes closed the gap. Ampbase runs their whole control plane on Tigris this way.
"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.