Re:Why Meteor will kill Ruby on Rails
by benaiah on Friday November 01, 2013 @05:42AM
(#6652712)
How is caching the count "cheating"? Grabbing the count for every request would be ridiculously expensive in any framework, not just Meteor.
[ Parent
| on HN ]
One count(*) query per request is not expensive at all. Suppose you cache the count and someone else adds rows to the collection. Your cached count is not getting updated and the whole reactivity concept breaks down since your app now thinks the row count is different from what it really is.