1. Cloud Constraints
Harper Reed
harper@nata2.org
@harper

2. Hi!

3. I build a lot of applications.

4. BIG

5. SMALL (ish)
supertrackr
fukung.net

7. Cloud Computing is Awesome

9. Cloud computing has a lot of
constraints
Architecture
Development
Deployment

10. Architecture
You never know if a resource
may disappear/fail.
Examples:
EC2 Instances
Cloud Server Resources

11. Development
The languages and supported
technologies may be limited
Examples:
App Engine: python/java
Heroku: ruby

12. Deployment
Old style simple deployment is
gone.
Examples:
App engine deploy tools
EC2 Tool chain
Heroku tool chain

13. Google App Engine

14. Google App Engine
A platform for developing and
hosting web applications in Google-
managed data centers.

15. App Engine
Time per request: 30 sec
Blobstore size: 2 GB
HTTP response size: 10 MB
Datastore item size: 1 MB
Application code size: 150
MB

16. Time per request
Limit the time allowed per request

17. Query Constraints
App Engine used to only return
resultsets with 1000 results.

18. Datastore
Often PaaS providers limit the
type and kind of queries you
can do over a datastore.
Joins are not your friend

19. Port 80
You can only serve and make requests on port 80.

20. Misc tools/apis
Queue
Search
Map Reduce
Datastore
Email
see: http://addons.heroku.com/

21. Servers
EC2 and Rackspace Cloud

22. Servers offer a lot of
freedom. They are also a pain
in the ass (don't trust them).

23. Architecture
Architecting server
infrastructures in clouded
environments is MUCH
different than the old fashioned
big iron way.
see: elastic scaling, IaaS vs PaaS

24. Cloud Server Constraints
Less constraints than PaaS
providers. Often emulates a
real server.
see: rackspace cloud

25. Some real constaints
Transient servers
Architect for failure
Deployment

26. Transient servers
Your servers may/will
disappear. You need to build
that assumption into your
infrastructure.

27. Architect for failure
When you don't control the
resource and hardware - you
will experience failures.
Build around the potential for
failure.

28. Deployment
The nature of cloud servers
let's you pop up 100s or 1000s
of boxes. This is a nightmare to
manage without awesome tools
like puppet, chef, etc.

29. The Magic

30. Work within these constraints even
when you don't have them
Your apps will be better.
They will respond better.
They will be more efficient.
Your users will be happier

31. ?
Questions
@harper
harperreed.org
harper@nata2.org