Cloud Tools for fun and Proﬁt! John McCaffrey RailsPerformance.com @J_McCaffrey
Agenda• Terminology• Deployment and hosting• Monitoring• Collaboration and Communication• Q&A
Why I love this stuff• Allows me to be fast• Show value, get feedback• Build a better product• Build conﬁdence, get more work
Terminology• Hosting: how/where the application lives• Deploy: update the application• Production: the ofﬁcial site• Staging: test/qa site that mimics prod.• VM: Virtual Machine• Git: Version control (GitHub.com)
Deployment• Getting that sucker out there!
Options• Self hosted• Amazon Web Services• EngineYard.com or RightScale.com• Heroku.com• https://appharbor.com
Self-Hosted Pro Con • Responsible for everything!• Control over everything! • High initial cost, unused• No surprises resources• Bare Metal (no additional • Upgrades, maintenance layers) • Security
Amazon Pro Con• Still a lot of control • Requires deep technical know-how to setup• Easy to scale up more instances • Responsible for various software updates• Pay as you go• No need to maintain • Responsible for some security components hardware• Free trial • Outages and surprises!
EngineYard.com Pro Con• Simpliﬁed and tailored to the most common needs• Easy to scale up more • Still requires some technical know-how to get started instances, Pay as you go• Full control over the OS • Responsible for various software updates• No need to maintain • Outages and surprises! hardware• Free trial
Heroku.com Pro Con• One line deployment• Free instance can go far • No control over underlying software, ports, etc• Easy to scale up more instances • Additional layers of routing• Pay as you go • Outages and surprises!• No need to maintain hardware or software
Heroku.com• Ruby/Rails, Java, Scala, Python• Free ‘dyno’ (aka single process)• Simple deployment• Lots of plugins and addons• Easy to experiment with