I'd love a more lightweight replacement for Neo4j but I need something that has good cypher support. Options are pretty limited.
> Use random strings at the start of your keys.
> This seems like a strange idea, but one of the implementation details
> of S3 is that Amazon use the object key to determine where a file is physically
> placed in S3. So files with the same prefix might end up on the same hard disk
> for example. By randomising your key prefixes, you end up with a better distribution
> of your object files. (Source: S3 Performance Tips & Tricks)
This is great advice, but just a small conceptual correction. The prefix doesn't control where the file contents will be stored it just controls where the index to that file's contents is stored. 12:47AM, Apr 21 - Event started, API impaired across all availability zones
12:00PM, Apr 21 - API recovered in non-affected zones
"Customers also experienced elevated error rates until Noon
PDT on April 21st when attempting to launch new EBS-backed
EC2 instances in Availability Zones other than the affected
zone."
12:30PM, Apr 22 - Nearly all volumes in affected zone restored
"all but about 2.2% of the volumes in the affected
Availability Zone were restored by 12:30PM PDT on
April 22nd"
18:15PM, Apr 23 - API restored for affected zone
"At 6:15 PM PDT on April 23rd, API access to EBS resources
was restored in the affected Availability Zone."
2012: 20:04, July 2 - Some number of racks lose power due to drained UPSs
21:10, July 2 - API restore
"8:04pm PDT to 9:10pm PDT, customers were not able to launch
new EC2 instances, create EBS volumes, or attach volumes in
any Availability Zone in the US-East-1 Region. At 9:10pm PDT,
control plane functionality was restored for the Region."
02:45, July 3 - Vast majority of volumes restored to customers
"By 2:45am PDT, 90% of outstanding volumes had been turned
over to customers."
http://aws.amazon.com/message/65648/
http://aws.amazon.com/message/67457/