Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Is this not the case already? Database drivers (or just your application code) are allowed to cache results if they like. The problem is cache invalidation.


Caches aren't the same. In the shard-in-memory case, the shard is the thing serving the queries, meaning it's not a cache it _is_ the live data.


Understood. For a single-node or read-only system it sounds fine, but then there are a variety of ways to solve that (e.g. a preloaded in-memory sqlite).




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: