Hacker News Reader

Comment by benhoyt | Hacker News Reader

1. You're right, it's somewhat apples and oranges. However, from what I can tell, that's part of the selling point of Tigris: you get CDN-like features "for free", without having to set up an extra layer like Cloudfront.

2. I actually do describe my concerns about durability near the end: https://benhoyt.com/writings/flyio-and-tigris/#disclaimer-an...

View on HN

1. It takes 10 mins to setup cloudfront with s3 as a source, heck 3 mins if one is experienced, it cannot be a selling point for a provider,

But having an s3 like provider directly inside fly.io, is a pretty cool selling point by itself :D

2. Indeed, noticed the disclaimer now, was just commenting overall in the hn post :D

Have a great day !

Hi, co-founder of Tigris here. There is a key difference between Tigris and a CDN. Tigris doesn't simply provide read caching like CloudFront. It allows what I call dynamic caching, i.e., you can literally update the object anywhere in the world, and any cached versions of the objects will be updated. So, I think of Tigris simply as a global object storage service, and the fact that it has caching built-in is more to provide fast performance and low latency than simply to mimic CDN behavior. But if you want to build a CDN, Tigris makes it trivial for a single developer to build a CDN.

> It allows what I call dynamic caching, i.e., you can literally update the object anywhere in the world, and any cached versions of the objects will be updated.

how much it typically takes to propagate the changes? Also what is the consistency model of the storage?

Reply on news.ycombinator.com