SQL db as cache – 2x faster* requests vs. Redis
dev.37signals.com
dev.37signals.com
A few more numbers to understand the load characteristics would be helpful, but that top line number is pretty impressive.
Yes, caching database queries in a database would be a groundbreaking technology
Note - I don't work there or use any of their products (other than Ruby on Rails). These are just my honest observations.
They have taken investment from Jeff Bezos decades ago.
https://medium.com/signal-v-noise/the-deal-jeff-bezos-got-on...
I understand DHH pisses off many people when he speaks, and some times he could probably be a bit less harsh, but I admire him a lot because he's one of the few people I know in this industry critically thinking, applying common sense, and not blindly following fads and all the bullshit that's going on at most places.
I think overall it is a net gain to follow and listen what he says, even if not said in the most "nice" way, I agree on almost everything he says tech wise.
And using Rails after years of pure "modern" SPAs, feels really refreshing. I'm sad most of us have forgotten how simpler things could be, and terrified about new people joining the industry that will never know it (for the time being at least).
So the real question is about cost/performance and picking the one that best fits your use case.
I also wonder how tweaking the backing DB's in memory cache will effect things.
Either way it's great to get this stuff out of the box with Rails and then be able to swap for Redis later if you observe that being a better fit.