5 ms·
If you've forgotten about NoSQL or BigData, chances are your shop really just overshot how much data and traffic they have.
by alharith 7y ago
If you've forgotten about NoSQL or BigData, chances are your shop really just overshot how much data and traffic they have.
- geofft 7y agoThe vast majority of shops have less data than the NoSQL vendors wanted to convince them they had. (With the ability to handle big data, some shops have started creating huge datasets e.g. as part of the targeted advertising arms race, but it's not clear they really need to.)
- flir 7y agoScale: the problem (almost) nobody has, and (almost) everybody wants.
- skrowl 7y agoDevs working at the vast majority of shops: Easily handle production load on 3-5 servers / VMs while reading all about how to script quickly spinning up 1,000 VMs if they really needed to.
- flir 7y agoMy servers are named after my pets and I'm not ashamed to admit it!
- yashap 7y agoThere’s different kinds of scale. I work for a company that has “only” hundreds of thousands of daily active users, but we ingest and persist a lot of data for them, on the order of millions of events per day for some of the larger users. We definitely run into big data problems in select services, despite not having a crazy number of users. Many companies are similar.
- snaky 7y agoOne modern PC server with PostgreSQL can handle about 1 mln transactions per second. http://akorotkov.github.io/blog/2016/05/09/scalability-towards-millions-tps/ http://akorotkov.github.io/blog/2016/05/09/scalability-towar...
- james_s_tayler 7y agoIn the comments the guy says the hardware the benchmark was running on had 3TB of RAM. That's not average hardware. It's a couple hundred connections max running select statements as fast as possible on the best hardware they could afford to test against. That doesn't translate into your CRUD app handling a million requests per second.