Rails Usergroup Hamburg: Heroku
by Ralph von der Heyden on Apr 20, 2010
- 1,681 views
Accessibility
Tags
More...Upload Details
Uploaded via SlideShare as Apple Keynote
Usage Rights
© All Rights Reserved
Statistics
- Favorites
- 0
- Downloads
- 6
- Comments
- 0
- Embed Views
- Views on SlideShare
- 1,595
- Total Views
- 1,681
* low barriers to entry
* low risk (cancel contract any time)
* e.g. fire up test systems for load tests and pay by the hour
* utility like electricity
* XING uses SSDs to quickly serve small image files (not possible with Amazon)
* low costs: variable costs, low risk
* security: experts take care of backups, it‘s their core business
* reliability: replicate data between cloud providers, fire up instances on the other if one is down
* heroku could switch the hosting provider any time without anyone noticing
* scalarium is tailored specifically to aws
* HTTP Cache: Varnish
* Routing Mesh: Custom, written in Erlang
* SQL: PostgreSQL
* Memcache
** better for peaks
** impacts by other users
* dedicated: 1 dedicated computing unit
* database.yml will be replaced automatically on deployment
http://my-url-35.heroku.com/
* e.g. no Redis
* every custom tool must be manually managed, out of the Heroku scope
* technical term confusion, e.g. bundle and migration