2. –
Distributed computing over a network enabling real
time communication and resource sharing.
™ Infrastructure (VMs, Servers, Storage, Load Balancer)
™ Platform (Web Server, Database, Execution run time)
™ Software (CRM, Email, Online Games)
Cloud Computing
3. –
™ IaaS – Google Compute Engine
(https://cloud.google.com/products/compute-engine)
™ PaaS – Google App Engine
(https://cloud.google.com/products/app-engine)
™ SaaS – Google Apps
(http://www.google.com/enterprise/apps/business/)
Google on the Cloud
4. –
™ Platform that is built on top of Google’s
infrastructure
™ Allows hosting web applications (and workers)
™ Run at Google’s Scale
™ Forget –
– Hardware failures
– OS upgrades
– Security patches
– Nightmares (may be?!)
Google App Engine
8. –
™ 10 applications per developer account
™ Code and Static Data Storage – 1GB
™ Stored Data – 1GB, 200 indexes max
™ 50000 Read and 50000 Write operations per day
™ 1 GB outgoing and 1GB incoming bandwidth daily
(Read more yourself -
https://developers.google.com/appengine/docs/
quotas?hl=en-EN )
Your free lunch!
9. –
For the business Gurus!
The reason why I've been invited to write this guest blog post is because
the site was built on Google App Engine and, according to Google
Analytics, it served about 3.4 million pageviews (1 million unique visitors)
in the 12 days it was live. It grossed over $1.2 million. Depending on who
you ask, this is quite a lot of traffic, and we exceeded the free App Engine
quota. Google sent us a bill for a grand total of $71.56.
-- Jeffrey Rossen, Wolfire Games
Ref:
http://googleappengine.blogspot.com/2010/06/how-app-engine-served-
humble-indie.html
Case of The Humble Indie Bundle
10. –
™ Tasks instead of native threads
™ No sockets
™ No native code
™ No write access to the system (Use Blob Store)
™ Limited access to libraries
™ 30 sec execution deadline
Technical Limitation