0
Heroku           Eberhard WolffArchitecture & Technology Manager             adesso AG
History & Origin
History & Origin•  Originally started as Ruby PaaS•  Now: Support for Node.js, Clojure,   Scala and Python•  Acquired by S...
Programming Model•  Jetty, Tomcat or Play! web server•  Worker for background activities•  Standard Java Programming Model
Scaling / High Availability•  Servers must be manually started for   scaling•  Failed servers will be restarted
Tools
Command Line Tool•  heroku•  E.g. creates new applications•  Other management functions  –  addons  –  logs  –  etc.
Other Tools•  heroku tool creates an empty git   repository•  Deploy new versions with git•  Build (maven) done by Heroku•...
Flexibility
Flexibility•  Dynos: processes run on Heroku•  Procfile defines command line to start a   “Dyno”•  Can be tuned and change...
Restrictions•  Max source and build artifact size:   100MB•  No sticky sessions•  Dynos may not use more than 512MB   RAM•...
Platform and other Services
Plattform•    Amazon Web Services•    US East region only•    Proven foundation•    Can use AWS resources as part of the  ...
Other Services•  Heroku supports Add-ons•  Postgresql and memcached by Heroku•  Many 3rd party•  E.g. relational databases...
Heroku: Highlights•  Very flexible: Supports many different   environments•  Broad range of additional services•  Also cov...
Heroku
Heroku
Heroku
Upcoming SlideShare
Loading in...5
×

Heroku

716

Published on

Short presenation about Heroku from WJAX 2012

Published in: Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
716
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
9
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Transcript of "Heroku"

  1. 1. Heroku Eberhard WolffArchitecture & Technology Manager adesso AG
  2. 2. History & Origin
  3. 3. History & Origin•  Originally started as Ruby PaaS•  Now: Support for Node.js, Clojure, Scala and Python•  Acquired by Salesforce.com
  4. 4. Programming Model•  Jetty, Tomcat or Play! web server•  Worker for background activities•  Standard Java Programming Model
  5. 5. Scaling / High Availability•  Servers must be manually started for scaling•  Failed servers will be restarted
  6. 6. Tools
  7. 7. Command Line Tool•  heroku•  E.g. creates new applications•  Other management functions –  addons –  logs –  etc.
  8. 8. Other Tools•  heroku tool creates an empty git repository•  Deploy new versions with git•  Build (maven) done by Heroku•  Build automatically deployed•  No specialized tools needed – git is enough•  Integration with Atlassian Bamboo possible
  9. 9. Flexibility
  10. 10. Flexibility•  Dynos: processes run on Heroku•  Procfile defines command line to start a “Dyno”•  Can be tuned and changed•  Can create custom “Buildpack” to run entirely different environments•  Available as Open Source e.g. for Ruby, PHP, Erlang, EmacsLisp…
  11. 11. Restrictions•  Max source and build artifact size: 100MB•  No sticky sessions•  Dynos may not use more than 512MB RAM•  I.e. max JVM heap about 400MB
  12. 12. Platform and other Services
  13. 13. Plattform•  Amazon Web Services•  US East region only•  Proven foundation•  Can use AWS resources as part of the solution•  750h per month free
  14. 14. Other Services•  Heroku supports Add-ons•  Postgresql and memcached by Heroku•  Many 3rd party•  E.g. relational databases, NoSQL databases, logging, caches…•  Configuration passed to service via environment variables
  15. 15. Heroku: Highlights•  Very flexible: Supports many different environments•  Broad range of additional services•  Also covers build
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×