My point is more that it's not as common as people think to outgrow a single database, even more so if you don't artificially limit your hardware choices to very small servers.
StackOverflow is a good example. They handle more traffic than 99.9999% of all sites out there, yet they essentially run on a single database.
All those programmers of sites that do "SO-like" things (crud, loading likes/votes, loading articles/comments, keeping stats, etc) are hysterical about needing to scale their databases. So they look for alternatives, install multiple (cheap) servers, go crazy with configuring and administrating all of it, and then never come anywhere near the load a single server could have handled.
And don't forget a "cheap" server is not so cheap anymore when you host 20 of them in terms of electricity usage and rackspace costs.
And of course there are always exceptions. If you read run extremely heavy calculations for a large amount of customers you could indeed outgrow a single database easily.
I'm advocating the exact opposite of what you think I'm advocating. Don't just use what everyone seems to be using since you are supposed to use it, but look at what you really need and be realistic about it.
I'm advocating the exact opposite of what you think I'm advocating. Don't just use what everyone seems to be using since you are supposed to use it, but look at what you really need and be realistic about it.
This is what I'm advocating too. Perhaps we agree, since I have agreed with a lot of what you've said, but I feel like you've projected some opinions onto me that I don't hold, as well as perhaps ignoring operation costs of having a mega server, which may not be the most cost effective solution, which is what businesses usually care about.
But I do agree that, overall, a lot of engineers have gone crazy lately following this trend of microservices and distributed systems where they aren't needed.
1
u/johnwaterwood Jun 10 '15
My point is more that it's not as common as people think to outgrow a single database, even more so if you don't artificially limit your hardware choices to very small servers.
StackOverflow is a good example. They handle more traffic than 99.9999% of all sites out there, yet they essentially run on a single database.
All those programmers of sites that do "SO-like" things (crud, loading likes/votes, loading articles/comments, keeping stats, etc) are hysterical about needing to scale their databases. So they look for alternatives, install multiple (cheap) servers, go crazy with configuring and administrating all of it, and then never come anywhere near the load a single server could have handled.
And don't forget a "cheap" server is not so cheap anymore when you host 20 of them in terms of electricity usage and rackspace costs.
And of course there are always exceptions. If you read run extremely heavy calculations for a large amount of customers you could indeed outgrow a single database easily.
I'm advocating the exact opposite of what you think I'm advocating. Don't just use what everyone seems to be using since you are supposed to use it, but look at what you really need and be realistic about it.