1. Rethinking Cost and Performance of Database Systems
David Redding
4/6/11

2. Introduction Why I picked this article What users want
Factors in building a Web Application
Old Database Architecture
New Proposed Database Architecture
Available Services 

3. Why I picked this article
Internship with T. Rowe Price Storage Team
Learned about cost and optimizations being done on the hardware side
Managing disk arrays and various storage devices

4. What users want Zero Cost Zero response time Infinite throughput
Infinite scalability
Users supported
Number of Machines added
100% predictability
Cost
Performance
Availability for read and write
Flexibility

5. Factors in building a database
Cost
No longer a one-time purchase
More hardware = More pay & Performance
Performance
Faster is better
Sustain a particular peak workload
Scalability
Step function
Predictability
Cost 
Consistency
Flexibility

6. Old Database Architecture
"Given a set of hardware resources and guaranteeing full data consistency, minimize the response time of requests and maximize the throughput of requests"

7. New Proposed Database Architecture
"Given performance requirements of an application (peak throughput; maximum tolerable response times), minimize the required hardware resources and maximize the data consistency"

8. Available Services Amazon Elastic Compute Cloud
Amazon Simple Storage Service
Sausalito

9. Extra sources http://aws.amazon.com/ http://aws.amazon.com/s3/