sharding

We hired some key employees from Flickr who knew a particular MySQL sharding strategy really well.

In terms of performance, perhaps you could: i) use domain sharding for pre-loading all the images.

Have you ever tried implementing sharding with all of your business logic in stored procedures?

As you said when sharding is possible you can just throw more boxes at it.

It replaces sharding's rebalancing, which usually requires a stop-the-world lock (or most of the world).

Basically as you scale relational databases, you end up sharding and loose a lot of the relational features, and basically end up with NoSQL.

Instagram's database sharding post was reasonably detailed and good at explaining things.

They can get away with sharding/colocating data that nobody else can.

Scenarios involving sprites and domain sharding we'd probably expect to fall somewhere in the middle.

When you destroy the centrality of reddit, even if by cutting out really bad stuff, you encourage the sharding of the web into isolated echo chambers.

Obviously, it will always depend on the particular queries you need, and on whether the graph has a natural cluster structure that can be used for sharding.

You also conveniently ignore the benefits of domain sharding and the fact that the CDN will serve the files faster and with lower latency than almost any setup.

The example I like to give is that of VoltDB, a "NewSQL" database written in Java and C++ (C++ for the core) which uses internal sharding.

Also people are spreading to 8chan, wizchan, krautchan and irc further sharding out the culture that created many of the things that we regard as "internet culture"

For example, the problem might be "What if our database becomes overloaded one day?" Choosing to implement, say, sharding, could lead to an over-engineered system which gets in the way of solving the many different future performance problems that could crop up.

> Each shard (the term sharding probably originated with UO) Probably, as the term "shard" was part of the backstory: a gem that contained the world ("Sosaria") was shattered, each shard then contained a version of Sosaria.

Sharding a database with stored procedures and constraints as you advise is a nightmare because you now have a completely separate deployment process [deploying stored procedures, if you think this doesn't require a deployment process across a sharded infrastructure...