Rails Usergroup Hamburg: Heroku

Heroku Rails Hosting in the Cloud

What is cloud computing?

Cloud Computing • Companies don‘t own the physical infrastructure • Computing time and storage is rented from a third party

Advantages • Variable costs instead of capital expenditure • Costs lining up with real usage • Real usage lining up with sales volume • Higher ﬂexibility

Disadvantages • You have to trust a third party • Limitations for exotic conﬁgurations

The Cloud rocks Deployment sucks

co sts agility low scala bility The Cloud rocks abso rb p ur ity eaks s ec reliability

Set up new Deal with instances outages Deployment sucks Persist d Bala ncing storag ant Loa e

Automate or die

Customers contract Dyno, SQL-Storage, Caching,… management ECS, S3, EBS, SimpleDB, …

Customers contract contract manages ECS, S3, EBS, SimpleDB, AppServer, SQL, etc. …

The Heroku stack

OS and Ruby • default: Debian 4 + Ruby 1.8.6 • optional: • Debian 5 + REE 1.8.7 • Debian 5 + Ruby 1.9.1

Dynos App servers, background processes

Database Shared or dedicated, based on PostgreSQL

Add-Ons • Amazon RDS • Websolr • Bundles (Backups) • Memcache • Cron • AMQP

Integration • Custom domains • New Relic • DNS servers • Sendgrid • Deploy hooks • SSL certiﬁcates • Exceptional • ...

Read Only FS • Caching → Header + Reverse Proxy • Uploads → S3 • SQLite → PostgreSQL • Ferret indices → use SOLR service

Interaction with heroku

Git based workﬂow • gem install heroku • heroku create • git push heroku master • heroku rake db:migrate

git push → build slug } • checkout master branch • download, build and install gems slug • delete .git, log/*, tmp/* and everything in .slugignore

Gem management • .gems manifest ﬁle • bundler (experimental)

Database management • Uses values from database.yml • Export to heroku → db:push • Import from heroku → db:pull

Other features • heroku • console (interactive/single commands) • rake

Conclusion

Cons • Oversimplification • Predefined sets of OS and Ruby version • No ssh access • No choice of physical location • Only predefined tools available • For larger setups: pretty expensive • Porting apps may be hard

Pros • Very simple start • Low costs in the beginning / for small apps • Offers simple management of complex apps, if developed with the heroku stack in mind

Questions? Follow me! @ralph

http://rvdh.de	53
http://www.slideshare.net	23
http://www.rvdh.de	8
http://localhost:4000	1
http://localhost	1

Rails Usergroup Hamburg: Heroku

by Ralph von der Heyden on Apr 20, 2010

Accessibility

Tags

Upload Details

Usage Rights

5 Embeds 86

Statistics

Rails Usergroup Hamburg: Heroku — Presentation Transcript