Hacker News Reader

Actually, not really. We checked the code to ensure that there was no gaming the system and it definitely APPEARS to be making separate database queries as we require in our rules. In fact, we had this same question in round 9 and had a number of people audit it. We cannot explain it other than it might be pretty darn fast.

View on HN

A better requirement would be to define some minimum level of durability, and some minimal level of freshness in the face of concurrent modifications.

Frankly, who cares if a caching driver avoids some database queries entirely if it still provides the same level of durability and freshness guarantees? If mongo+redis are OK, what's wrong with a plain hashtable?

The benchmark requirements aren't specific about durability requirements of the database. https://www.techempower.com/benchmarks/#section=code

This is where a difference between Redis and other databases will exist depending on configuration.

Reply on news.ycombinator.com