logoalt Hacker News

auspivyesterday at 6:49 PM4 repliesview on HN

I think the question is probably more along the lines of - why not do a database with 100 TB of storage/records instead of a cache? tomato / tomato.. especially with smart caching in front of database. 100TB of flash is a good bit cheaper than 100TB of memory


Replies

ecnahc515yesterday at 7:19 PM

Because it would be slower and have different scaling requirements than the ones they want.

pocksuppetyesterday at 9:41 PM

It's not 100TB of data. It's probably 50 GB of data on each of 2000 servers. Because it's a cache. What is the point of a central cache if it's as slow to access as the original data?

show 1 reply
fc417fc802yesterday at 7:51 PM

I'm no expert but presumably all of throughout, latency, and churn. DNS is approximately a giant KV store where the typical record has a TTL of ~5 minutes.

robotresearcheryesterday at 8:25 PM

This is smart, task-specific caching in front of database.