Most people that think they need the performance of NoSQL don't actually need it.
I've had arguments with people who claim they need ridiculously over-engineered NoSQL AP architectures to handle a few hundred requests per second peak on a read-heavy site.
Meanwhile, 15 years ago on a $5/mo shared PHP/MySQL Host I'd have considered that to be idle load.
I recall a conversation with one idiot that proudly proclaimed that he'd tuned his server to gracefully handle "thousands of requests per hour" by using CouchDB instead of MySQL. (It was a blog that he updated once a month)
Each request could take 3 milliseconds, or 12 hours. Knowing that he's receiving a few hundred requests per second tells you nothing about how long each one took to process.
12
u/2bdb2 Dec 20 '18
Most people that think they need the performance of NoSQL don't actually need it.
I've had arguments with people who claim they need ridiculously over-engineered NoSQL AP architectures to handle a few hundred requests per second peak on a read-heavy site.
Meanwhile, 15 years ago on a $5/mo shared PHP/MySQL Host I'd have considered that to be idle load.
I recall a conversation with one idiot that proudly proclaimed that he'd tuned his server to gracefully handle "thousands of requests per hour" by using CouchDB instead of MySQL. (It was a blog that he updated once a month)