Your SlideShare is downloading. ×
Heroku for-team-collaboration
Upcoming SlideShare
Loading in...5

Thanks for flagging this SlideShare!

Oops! An error has occurred.

Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Heroku for-team-collaboration


Published on

1 Like
  • Be the first to comment

No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

No notes for slide
  • Maybe a venn diagram to illustrate these definitions better?
  • ----- Meeting Notes (16/01/2013 11:59) ----- Create a new app via the website & on the command line. Show the addon market place, apps control panel & the dev center.
  • Transcript

    • 1. Team collaboration in the Cloud John Stevenson Developer Advocate @ Salesforce / Heroku
    • 2. Safe Harbor Safe harbor statement under the Private Securities Litigation Reform Act of 1995: This presentation may contain forward-looking statements that involve risks, uncertainties, and assumptions. If any such uncertainties materialize or if any of the assumptions proves incorrect, the results of, inc. could differ materially from the results expressed or implied by the forward-looking statements we make. All statements other than statements of historical fact could be deemed forward-looking, including any projections of product or service availability, subscriber growth, earnings, revenues, or other financial items and any statements regarding strategies or plans of management for future operations, statements of belief, any statements concerning new, planned, or upgraded services or technology developments and customer contracts or use of our services. The risks and uncertainties referred to above include – but are not limited to – risks associated with developing and delivering new functionality for our service, new products and services, our new business model, our past operating losses, possible fluctuations in our operating results and rate of growth, interruptions or delays in our Web hosting, breach of our security measures, the outcome of intellectual property and other litigation, risks associated with possible mergers and acquisitions, the immature market in which we operate, our relatively limited operating history, our ability to expand, retain, and motivate our employees and manage our growth, new releases of our service and successful customer deployment, our limited history reselling products, and utilization and selling to larger enterprise customers. Further information on potential factors that could affect the financial results of, inc. is included in our annual report on Form 10-Q for the most recent fiscal quarter ended April 30, 2011. This documents and others containing important disclosures are available on the SEC Filings section of the Investor Information section of our Web site. Any unreleased services or features referenced in this or other presentations, press releases or public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make the purchase decisions based upon features that are currently available., inc. assumes no obligation and does not intend to update these forward-looking statements.Proprietary & Confidential
    • 3. Why consider Heroku ?
    • 4. Challenging deployment “Ops teams are overwhelmed by developer requests”“Different environments are not always the same. Patching and internal processes often not automated” “There is a divide in many enterprises between the developers & operations teams.”
    • 5. Continuous Delivery“..reducing the cycle time between an idea and usable software” - Martin Fowler “Software delivers no revenue until it is in the hands of its users.” -Jez Humble “.. leads to deeper relationship between IT, their business customer, and their final customers.” -Jez Humble
    • 6. Cloud Services should be easy“Should have a natural way to use the services that fits into each teams existing workflow” “Should be easy to see the value & cost benefits” “Should be as trust worthy as any internal service, if not more so.”
    • 7. 30 second app - Demo
    • 8. 30 second app
    • 9. What is Heroku ?
    • 10. 4 core principlesForget Run See Trust &Servers Anything Everything Manage
    • 11. What is Heroku ?Forget servers
    • 12. Introducing Dynos A self contained resource in which to run your applicationA logical abstraction over servers scalability is more valuable than # of serversAllows a trivial way to scale your app and know how much its costing you!
    • 13. For DevelopersFree:750 hours per month per appHave as many apps as you require
    • 14. Scaling via web control panel
    • 15. Inside an Heroku Dyno Embedded • Jetty, Tomcat, etc Container ApplicationDependencies • Maven, Gradle, SBT, Leiningen, Bundle, etc. YourApplication • Anyapplication code • Any framework (Spring, Play!, django, compojure,etc.)
    • 16. Forget ServersFocus 100% on codeFully managed platformTrust Heroku to be your DevOps support
    • 17. What is Heroku ?Run Anything
    • 18. An Elastic “polyglot” Platform-as-a-Servicepol·y·glot [pol-ee-glot]adjective1. able to speak or write several languages; multilingual.2. containing, composed of, or written in several languages: apolyglot Bible.
    • 19. “Supported” languagesA Polyglot platform: 6 supported languages
    • 20. Additional support through “Build packs”Control your own build, deploy & run cycle defined using shell script or rubyCreate your app with a build pack heroku create myapp --buildpack
    • 21. Many build packs on Github
    • 22. Polyglot environmentsSinatra Ruby on Rails Play! Mongo DB Amazon RDS Postgres Ruby Clojure Node.JS Spring LiftWaves Halcyon Noir Couch DB RedisPadrino Ring Compojure Java Scala Open Open Frameworks Open Languages Databases
    • 23. No Vendor Lock-inProcfile A simple, declarative way to define app process types, so they can be easily managed in unison. A text file in the root of your project containing a startup command & parameters
    • 24. Procfile examplesSimple web serverweb: python -m SimpleHTTPServer $PORTClojureweb: lein with-profile production trampoline run -m my-clojure-website.web
    • 25. Procfile examplesJava, Play framework & Postresweb: target/start -Dhttp.port=${PORT}${JAVA_OPTS} -DapplyEvolutions.default=true -Ddb.default.driver=org.postgresql.Driver -Ddb.default.url=${DATABASE_URL}
    • 26. What is Heroku ?See Everything
    • 27. logplexUnified logging• App operations• Administrative commands• All infrastructure messagesReal time Dyno information
    • 28. Logplextime-ordered events aggregated from the output streams of all your app’s running processes, system components, and backing services.heroku logs
    • 29. heroku logsheroku logs --source appsheroku logs --source herokuheroku logs --source heroku --ps api
    • 30. Example of error in logs
    • 31. Trust & manage
    • 32. Effortless ScalingWeb WorkerWorkload Diversity (Process types)
    • 33. Scaling your app$ cat Procfileweb: java $JAVA_OPTS EmbeddedServerworker: java $JAVA_OPTS YourJavaClass$ heroku scale web=4 worker=10Scaling processes... done
    • 34. Control apps via
    • 35. Controling Heroku - CLI$ heroku psProcess State Command----------- ----------- -----------------------------web.1 up for 6s java $JAVA_OPTS EmbeddedServerworker.1 up for 5s java $JAVA_OPTS YourJavaClass$ heroku restart worker.1Restarting worker.1 process... Done$ heroku status=== Heroku StatusDevelopment: No known issues at this time.Production: No known issues at this time.$ heroku sharing=== enterprise-workshop
    • 36. Trust & Manage 24x7 platform monitoring Herokai know when there is trouble before you do!
    • 37.
    • 38. Heroku cost calculator
    • 39. What else is there to Heroku ?Heroku add-ons
    • 40. Extensibility A range of Relational & NoSQL databases Monitoring for your app …and too much to cover here
    • 41. Postgres as a servicePowerful data storage Irrespective of if you app is deployed on Heroku
    • 42. Git Push DeployGetting started with Heroku
    • 43. Setup your Heroku accountCreate an account on HerokuDownload the Heroku ToolbeltUpload you public key heroku login
    • 44. Whats in the Toolbelt?Heroku command line tools create | logs | ps | releases | run | addons | configA Git clientForeman run apps locally as they would run on Heroku
    • 45. 5 steps to first deployCreate you app (using your build tool)Initialise a git repository for your projectCreate your heroku appCommit your files to the local repositoryPush your app to heroku
    • 46. SimplisticContinuous deployment
    • 47. Continuous deployment
    • 48. Github and HerokuCollaboration in the cloud
    • 49. Heroku CollaborationAdd multiple developers to an app
    • 50. Heroku CollaborationAll collaborators can: push updates & trigger deployment view and change app settingsOnly Owners can delete the app or transfer ownership to a different account
    • 51. Github – Social CodingCollaborate on public or private projects Collaborate 24/7 all over the world
    • 52. Add Github repo to your appCreate a new repo on GithubAdd the repo to your project git remote add github you code to github git push –u github master
    • 53. Collaborative coding on GithubAdd people to your Github repo only those that you trust!Encourage pull requests allows collaboration around commits Facilitate code reviews
    • 54. Pull request discussion
    • 55. Pull request code review
    • 56. Adding more environmentsTypically there are: production, staging, uat, testing , devCreate the environments you want heroku create my-app-staging heroku create my-app-uat heroku create my-app-testing
    • 57. Check your addons firstCheck which addons used before creating new environmentsheroku addons --remote herokuheroku addons --remote production
    • 58. More Envs = more reposEvery time you create a new Heroku environment a remote git repository is addedgit remote –v
    • 59. Managing multiple reposLearn to love git log Configure it to use –graphOr get a good visual git tool SourceTree for MacOSX is great (and free)
    • 60. git log --graph
    • 61. Heroku behind HEAD
    • 62. Continuous Integration servers
    • 63. Continuous deployment
    • 64. Travis-CI for open projects
    • 65. Managing DeploymentRolling back your applications
    • 66. Heroku rollback mechanism
    • 67. Release History
    • 68. View info about a release
    • 69. Rollback to a specific version
    • 70. History after rollback & push
    • 71. Try for yourself
    • 72. Thank you !!!