1. Google AppEngine vs. Amazon EC2/S3
Summary of dinner discussion

2. The Systems Today Python BigTable Other API’s VMs Flat File Storage
AppEngine:
Higher-level functionality (e.g., automatic scaling)
More restrictive (e.g., respond to URL only)
Proprietary lock-in
EC2/S3:
Lower-level functionality
More flexible
Coarser billing model
June 3, 2008
Google AppEngine vs. Amazon EC2/S3

3. Will The Two Models Converge?
Amazon:
Add more proprietary APIs?
Google:
Support more languages, storage mechanisms?
June 3, 2008
Google AppEngine vs. Amazon EC2/S3

4. Google AppEngine vs. Amazon EC2/S3
What is “The Platform”?
Application-specific code
Libraries: shared by multiple applications
Platform: same for all applications
June 3, 2008
Google AppEngine vs. Amazon EC2/S3

5. How Will The Market Evolve?
Most markets end up dominated by 3-5 entrenched players:
1 Gorilla: 60-80% of market
1 Chimp: 20-30% of market
1-3 Wimps: 1-10% of market
Hard to create a monopoly:
Weak network effect?
APIs will create some lock-in, but aren’t Web applications short-lived?
Buy market share for new stack with discount rates?
Create ecosystem of 3rd-party library developers?
Windows vs. Macintosh comparison?
June 3, 2008
Google AppEngine vs. Amazon EC2/S3

6. Google AppEngine vs. Amazon EC2/S3
Making a Choice
Researchers will pick Amazon:
Fewer restrictions
Easier to try out new ideas
Application developers:
If AppEngine meets all your needs, it will probably be easier to use.
If AppEngine doesn’t meet your needs, it may be hard to extend.
June 3, 2008
Google AppEngine vs. Amazon EC2/S3