Heroku + Java

A talk on What is Heroku and how Heroku+Java for St. Louis Java Users Group

Transcript

2. Clint Hello! my name is
4. Deploying Applications with Heroku
6. ❖ What is Heroku ❖ 12 Factor Apps ❖ Working With Heroku ❖ Heroku + Java Contents:
7. What Is Heroku
8. Heroku is a Cloud!
9. Heroku is a PaaS: “Platform as a service (PaaS) is a category of cloud computing services that provide a computing platform and a solution stack as a service [...] The consumer controls software deployment and configuration settings. The provider provides the networks, servers, storage and other services." ! - https://en.wikipedia.org/wiki/Platform_as_a_service
10. WE RUN FOR YOU ~YOUR CODE~
11. History: ❖ Founded June 2007, supporting Rack-compatible projects ❖ December 2010: acquired by Salesforce.com ❖ July 2011: Yukihiro "Matz" Matsumoto joined as Chief Architect, Ruby ❖ May 2011: Cedar stack announced ❖ <3 August 2011: Java support <3
12. Supporting: ❖ Ruby ❖ Python ❖ ->Java<- ❖ Node.js ❖ Clojoure ❖ PHP …and basically anything with 3rd Party Buildpacks
13. HOW
14. This:
15. This: Apps
16. Apps: ❖ application, not infrastructure ❖ dynamic and distributed runtime ❖ utilizes process-based execution model ❖ strict separation of apps and their dependencies ❖ embodiment of 12 Factor methodology
17. RECAP: What is Heroku? Platform + Apps
18. 12 Factor Apps
19. <alt> Architecting Apps for Heroku
20. Philosophy:
21. I. Codebase II. Dependencies III. Config IV. Backing Services V. Build, release, run VI. Processes VII. Port binding VIII. Concurrency IX. Disposability X. Dev/prod parity XI. Logs XII. Admin processes 12 Factor Apps Philosophy:
22. I. Codebase II. Dependencies III. Config IV. Backing Services V. Build, release, run VI. Processes VII. Port binding VIII. Concurrency IX. Disposability X. Dev/prod parity XI. Logs XII. Admin processes 12 Factor Apps Philosophy:
23. Codebase
24. ❖ Single repo ❖ One codebase tracked in revision control ❖ Many deploys Codebase:
25. Dependencies
26. ❖ Consistent packaging: RubyGems, pip, npm, Maven ❖ Declaration: Gemfile, requirements.txt ❖ Execution isolation: bundle exec, Virtualenv Dependencies:
27. Config
28. ❖ Resource handles ❖ Credentials ❖ Things you used to use constants for ❖ All your secrets Config:
29. Backing Services
30. ❖ Datastores: MySQL, Postgres ❖ Queueing systems: RabbitMQ ❖ Some local, other remote ❖ Can be attached/detached Backing Services:
31. Processes
32. ❖ Stateless processes ❖ Persistence/ communication: backing services Processes:
33. Logs
34. ❖ Treat logs as event streams ❖ Visibility into running app ❖ write to stdout ❖ collected by execution environment Logs:
35. RECAP: Twelve-Factors Apps I. Codebase II. Dependencies III. Config IV. Backing Services V. Build, release, run VI. Processes VII. Port binding VIII. Concurrency IX. Disposability X. Dev/prod parity XI. Logs XII. Admin processes
36. Working With Heroku
37. This:
38. ❖ git push ❖ slug compilation ❖ dyno provisioning ❖ api/routing updates ❖ CLI for management (overly simplistic) This:
39. About Dynos
40. This:
42. Small sharp tools
43. Many identical copies (dynos)
44. Dynos: ❖ lightweight containers ❖ Elasticity & scale ❖ Management ❖ Distribution and redundancy
45. Many identical copies (dynos)
46. Java environment your app Java environment your app postgres your data add-on your data
47. This:
48. Add-ons
49. ❖ Data Stores: Postgres, MongoHQ, Redis ❖ Search: Websolr, Flying Sphinx ❖ Logging: Paptertrail, Loggly ❖ Analytics: New Relic, Blitz ❖ Queue Managers: IronMQ, Pusher ❖ Cache: Memcache, RedisGreen Add-ons:
50. Add-ons:
51. $ Pricing $
52. Pricing: ❖ Based on usage ❖ 750 free dyno hours ❖ Add-ons are prorated based on plan ❖ One-off dynos accrue too
53. ^ Up Time ^
54. Uptime:
55. Uptime: ❖ 99% since December 2012 ❖ 99.9% for all of 2013 (so far) ❖ Based on # of apps affected ❖ https://status.heroku.com ❖ https://status.heroku.com/uptime
56. RECAP: • Spend time solving app problems, not infrastructure • Add things as needed • Pay by usage • 99.9% uptime
57. Heroku JAVA
58. ❖ Development ❖ Packaging ❖ Distribution ❖ Install ❖ Deployment Classic Approach:
59. ❖ Development ❖ Packaging ❖ Distribution ❖ Install ❖ Deployment Heroku Approach:
60. ❖ No application server ❖ Linked libraries ❖ Minimal external configuration ❖ Still have Servlet, JSP, JDBC Heroku Approach:
61. Application Servers?
62. ❖ Deployment ❖ Start/stop/restart ❖ Deployment of changes ❖ Clustering (scaling) Application Servers: ❖ Load-balancing ❖ Failover ❖ Logging ❖ Service binding
63. ❖ Deployment ❖ Start/stop/restart ❖ Deployment of changes ❖ Clustering (scaling) Application Servers: ❖ Load-balancing ❖ Failover ❖ Logging ❖ Service binding Heroku
64. Demo!
65. ❖ devcenter.heroku.com/articles/getting- started-with-spring-mvc-hibernate ❖ https://github.com/heroku/devcenter- spring-mvc-hibernate Demo!
66. Heroku Java Recap: ❖ Build for deployment, not packaging ❖ Version control for distribution ❖ Heroku is the Application Server ❖ Think Applications, not systems
67. What Now?
68. 1.Sign up at www.heroku.com 2.toolbelt.heroku.com 3.devcenter.heroku.com/categories/java 4.$ heroku create 5.$ git push heroku master 6.discussion.heroku.com/category/java
69. my twitter is @ctshryock my email is clint@heroku.com Thanks!