I ask, "what's the best thing and the worst thing about your job?" Someone asked me that once, and I thought it was a great question, so I stole it.
Disagree. The point of this article as I understood it was not to provide short advice, but to provide a comprehensive explanation of the problem and why the 3 listed solutions are good ones. People often ask "why use…
Why can't the hosted service use an "encrypted file in the cloud" as its implementation? As long as it requires client-side code to do the decryption, the key stays in your head alone.
[1] looks like an example where the data didn't fit in RAM. Mongo works best when data fits in RAM or if you use SSD's. Yes, it's sub-optimal. [2] is from a year and a half ago. It doesn't belong in a sentence that…
I disagree that sharding can ever be a trivial problem if you're going to try to tackle moving data between shards while staying online. I'm not saying it's impossible, just that it's not trivial.
An example is stack overflow. They've been able to scale up instead of scaling out. http://highscalability.com/blog/2009/8/5/stack-overflow-arch... is the link I can find right now.
My definition of seriousness includes some relatively large scale. Your definition of seriousness appears to mean any site that is important to the person or business running it. Is that a fair assessment? I think your…
Sorry, those were meant to be examples, not an exhaustive list.
Good point.
Fair, my statement was overly broad. Sites that are read-only or store blob data in something like S3 can often avoid sharding for quite a while and rely on machines to just get bigger over time. That said, if your site…
I don't know if it's the _most_ important feature, but I wouldn't build a serious site on top of anything that didn't have some sort of built-in sharding story. With postgres you have to roll your own. If you want to…
Unless he's planning to build sharding on postgres too, I think he's missing the point.
The implication is that the Great Firewall will see a GET for google.com/search?q=[any of those characters] (or equivalent) and not let you get to google for a minute afterward.
I ask, "what's the best thing and the worst thing about your job?" Someone asked me that once, and I thought it was a great question, so I stole it.
Disagree. The point of this article as I understood it was not to provide short advice, but to provide a comprehensive explanation of the problem and why the 3 listed solutions are good ones. People often ask "why use…
Why can't the hosted service use an "encrypted file in the cloud" as its implementation? As long as it requires client-side code to do the decryption, the key stays in your head alone.
[1] looks like an example where the data didn't fit in RAM. Mongo works best when data fits in RAM or if you use SSD's. Yes, it's sub-optimal. [2] is from a year and a half ago. It doesn't belong in a sentence that…
I disagree that sharding can ever be a trivial problem if you're going to try to tackle moving data between shards while staying online. I'm not saying it's impossible, just that it's not trivial.
An example is stack overflow. They've been able to scale up instead of scaling out. http://highscalability.com/blog/2009/8/5/stack-overflow-arch... is the link I can find right now.
My definition of seriousness includes some relatively large scale. Your definition of seriousness appears to mean any site that is important to the person or business running it. Is that a fair assessment? I think your…
Sorry, those were meant to be examples, not an exhaustive list.
Good point.
Fair, my statement was overly broad. Sites that are read-only or store blob data in something like S3 can often avoid sharding for quite a while and rely on machines to just get bigger over time. That said, if your site…
I don't know if it's the _most_ important feature, but I wouldn't build a serious site on top of anything that didn't have some sort of built-in sharding story. With postgres you have to roll your own. If you want to…
Unless he's planning to build sharding on postgres too, I think he's missing the point.
The implication is that the Great Firewall will see a GET for google.com/search?q=[any of those characters] (or equivalent) and not let you get to google for a minute afterward.