Annie Sexton

Yeah. So Tigris is built on top of Fly's infrastructure, and that's what allows it to be globally distributed. I do have a video on this, but basically the way it works is whenever, like, let's say a user uploads an asset to a particular bucket. Well, that gets uploaded directly to the region closest to the user. Whereas with a CDN, there's sort of like a centralized place where

Yeah. So Tigris is built on top of Fly's infrastructure, and that's what allows it to be globally distributed. I do have a video on this, but basically the way it works is whenever, like, let's say a user uploads an asset to a particular bucket. Well, that gets uploaded directly to the region closest to the user. Whereas with a CDN, there's sort of like a centralized place where

assets need to get copied to. And then eventually they get sort of trickled out to all of the different global locations. Whereas with Tigris, the moment you upload something, it's available in that region instantly. And then it's eventually cached in all the other regions as well as it's requested. In fact, with Tigris, you don't even have to select which regions things are stored in.

assets need to get copied to. And then eventually they get sort of trickled out to all of the different global locations. Whereas with Tigris, the moment you upload something, it's available in that region instantly. And then it's eventually cached in all the other regions as well as it's requested. In fact, with Tigris, you don't even have to select which regions things are stored in.

You just get these regions for free. And then on top of that, it is so much easier to work with. I feel like the way they manage

You just get these regions for free. And then on top of that, it is so much easier to work with. I feel like the way they manage

permissions the way they handle bucket creation making things public or private is just so much simpler than other solutions um and the good news is that you don't actually need to change your code if you're already using s3 it's s3 compatible so like whatever sdk you're using is probably just fine and all you got to do is update the credentials so it's super easy

permissions the way they handle bucket creation making things public or private is just so much simpler than other solutions um and the good news is that you don't actually need to change your code if you're already using s3 it's s3 compatible so like whatever sdk you're using is probably just fine and all you got to do is update the credentials so it's super easy