Evernote Architecture - 9 Million Users and 150 Million Requests a Day
highscalability.com
highscalability.com
Also, an extra layer (memcached) in front of mysql for caching requests could save them lots of nodes if reads are dragging down performance/requiring more nodes to spread read load.
Evernote shard their 9.5 million total users across 90 shards, where each shard is represented by two of the four or four drives in a mirrored RAID.
Also, they are using Ehcache as their object-caching layer, which we can assume is their alternative to memcached. The choice between the two probably coming down to sticking to their Java stack.
I'm sure we'll here more in the promise of future articles focusing more on individual subsystems, as the article is pretty shallow in connecting the dots.
I hate to sound like a dick, but anyone who has dealt with large scale web apps would consider this a starting point, not worthy of a architecture presentation.
EDIT: Ah ha. Having never used Evernote before, they didn't make it very clear that they are essentially trying to build a SAN. I assumed they were storing plain text notes like stickies.
That's a completely meaningless statement if you don't specify what the requests do, and the resources available to make it happen.