The core parts of relational databases are transactions, tables, and indices. At Tigris we use a non-relational database (FoundationDB) but still have indices. How did we do it? We made our own!
Today we have a romp through database theory and how indices get implemented on top of FoundationDB so you can learn more about how the tools you use work. Enjoy!
Read more on the blog: tigrisdata.com/blog/fdb-indi…
Ram is inordinately expensive right now, so everything we can do to cut ram usage makes objgit better for everyone.
Look in the thread for the post because social networks punish you for having thread starting posts with links in them for some reason.
As such, here's a tale of how objgit's ram usage was cut by an exponential amount scaled to repository size: tigrisdata.com/blog/objgit-r…
Tigris Data retweeted
Wow Railway Buckets so good.
I benchmarked 5 object storage providers from 6 locations around the world
I included:
- @awscloud S3
- @Cloudflare R2
- @Railway Buckets
- @Backblaze B2
- @neondatabase Storage
It used Files SDK to make it as fair as possible
Here's a summary 👇 (this is also a thread)
Tigris Data retweeted
Gave the Bucket file explorer an overhaul on @prisma Compute. It can bulk upload and delete, do prefix filtering and understands folders. And it's gorgeous!
Prisma Buckets are powered by @TigrisData so they are blazing fast. Free for the rest of the year, so give it a try!
Tigris Data retweeted
TAG is a self-hosted cache for object storage, and it is open source.
Replying to @ovaistariq
Håkon and Jeff wrote up the whole design, Vortex files, SlateDB indexes on object storage, and TAG as the cache: goldsky.com/blog/prism-geo-r…
Hey all, we have more updates on objgit!
Looks like it's taking off amidst other companies making git services for some reason. Again, really have to wonder what that's all about.
Either way we want to keep chugging along at this and turn objgit into the git server that we wish we had: infinitely scalable and with all the important data on object storage. As an added bonus we'd also try to make a scraper-resistant web UI.
To learn more, look at the blog: tigrisdata.com/blog/objgit-v…
9ms point lookups without running your own database in every region
That's what @goldskyio built with Tigris, @vortexdotdev, and SlateDB
Get our side of the story 👇
Tigris Data retweeted
My favorite number in this writeup is 9ms. That is a point lookup served through a cache out of object storage, not a database. Goldsky runs billions of these against one copy of the chain on Tigris.
Not long ago I'd have called building your own data lake format a waste of an engineering team's time.
We built one anyway 🤡
It has been powering all our core products for months, and I'm excited to share how we did this.
goldsky.com/blog/prism-geo-r…
Tigris Data retweeted
Yup, good catch. @prisma now uses Prisma Postgres instead of Turso because why wouldn't we. 🐶🥫
@TigrisData is what we use for Prisma Storage: prisma.io/docs/storage









