Download as PDF, PPTX
Uploaded byJoe Kutner
JavaOne 2015: 12 Factor App
The document discusses best practices for modern Java application deployment based on the 12 Factor App methodology. It covers topics like packaging applications as JAR files instead of WAR files, managing dependencies, separating configuration from code, building in an automated and isolated way, making processes stateless and portable, enabling concurrency, and achieving parity between development and production environments. The 12 factors of the methodology are also listed and described.
More Related Content
Similar to JavaOne 2015: 12 Factor App
JavaOne 2015: 12 Factor App
- 1. 12 Factor App Best Practicesfor Java Deployment
- 2. You might notlike what I have to say
- 3.
- 4.
- 5.
- 6.
- 7. 2005 2015 WAR filesJAR files App Servers Microservices Hot Deploy Continuous Deploy Server in a closet Heroku/AWS/etc
- 8.
- 9. 12 Factor App amethodology Scalability Maintainability Portability
- 10.
- 11. • Codebase • Dependencies •Config • Backing services • Build, release, run • Processes • Port Binding • Concurrency • Disposability • Dev/Prod Parity • Logs • Admin Processes 12 Factor App
- 12. • Codebase • Dependencies •Config • Backing services • Build, release, run • Processes • Port Binding • Concurrency • Disposability • Dev/Prod Parity • Logs • Admin Processes 12 Factor App
- 13.
- 16.
- 17.
- 18.
- 19.
- 20. • Codebase • Dependencies •Config • Backing services • Build, release, run • Processes • Port Binding • Concurrency • Disposability • Dev/Prod Parity • Logs • Admin Processes 12 Factor App
- 21. Never rely onimplicit existence of system-wide packages Explicitly declare and isolate dependencies
- 22.
- 24.
- 25.
- 26.
- 27. build.gradle task copyToLib(type: Copy){ into "$buildDir/server" from(configurations.compile) { include "jetty-runner*" } }
- 28. • Codebase • Dependencies •Config • Backing services • Build, release, run • Processes • Port Binding • Concurrency • Disposability • Dev/Prod Parity • Logs • Admin Processes 12 Factor App
- 29. • Resource handlesto the database, memcached, and other backing services • Credentials to external services such as Amazon S3 or Twitter • Per-deploy values such as the canonical hostname for the deploy Anything that changes between deployment environments: (does not include things like conf/routes) Configuration is…
- 30. Configuration should be strictlyseparated from code
- 31.
- 33. Configuration belongs in theenvironment, not in the application
- 34. applicationContext.xml <bean class="org.apache.commons.dbcp.BasicDataSource" destroy-method="close" id=“dataSource"> <property name="driverClassName"value="org.postgresql.Driver"/> <property name="url" value=“${JDBC_DATABASE_URL}"/> // ...
- 35.
- 36. Can you makeyour app open source at any moment, without compromising any credentials? Litmus Test
- 37. • Codebase • Dependencies •Config • Backing services • Build, release, run • Processes • Port Binding • Concurrency • Disposability • Dev/Prod Parity • Logs • Admin Processes 12 Factor App
- 39.
- 40. • Codebase • Dependencies •Config • Backing services • Build, release, run • Processes • Port Binding • Concurrency • Disposability • Dev/Prod Parity • Logs • Admin Processes 12 Factor App
- 41.
- 42. $ mvn cleaninstall $ sbt stage $ ./gradlew build build
- 43. $ heroku deploy:jar-j myapp.war $ mvn heroku:deploy $ docker push ... release
- 44. $ java -jarmyapp.war $ build/install/myapp/bin/myapp.bat run $ mvn jetty:run $ service tomcat start $ cp myapp.war TOMCAT_HOME/webapps/
- 45. $ git pushheroku master build, release, & run
- 46.
- 47. • Codebase • Dependencies •Config • Backing services • Build, release, run • Processes • Port Binding • Concurrency • Disposability • Dev/Prod Parity • Logs • Admin Processes 12 Factor App
- 48.
- 49.
- 50. • Codebase • Dependencies •Config • Backing services • Build, release, run • Processes • Port Binding • Concurrency • Disposability • Dev/Prod Parity • Logs • Admin Processes 12 Factor App
- 51. The twelve-factor app iscompletely self-contained The web app exports HTTP as a service by binding to a port
- 52.
- 53.
- 54.
- 55. • Codebase • Dependencies •Config • Backing services • Build, release, run • Processes • Port Binding • Concurrency • Disposability • Dev/Prod Parity • Logs • Admin Processes 12 Factor App
- 56. Relax bro, Igot this… java.util.concurrent RxJava java.util.stream
- 57.
- 58.
- 59. • Codebase • Dependencies •Config • Backing services • Build, release, run • Processes • Port Binding • Concurrency • Disposability • Dev/Prod Parity • Logs • Admin Processes 12 Factor App
- 60.
- 61. Servers are notpets Servers are cattle
- 62.
- 63.
- 64.
- 65.
- 66. Easy to replace Decoupledfrom external infrastructure Easy to modify
- 67.
- 68. • Codebase • Dependencies •Config • Backing services • Build, release, run • Processes • Port Binding • Concurrency • Disposability • Dev/Prod Parity • Logs • Admin Processes 12 Factor App
- 69.
- 70.
- 71.
- 72.
- 73.
- 74. • Codebase • Dependencies •Config • Backing services • Build, release, run • Processes • Port Binding • Concurrency • Disposability • Dev/Prod Parity • Logs • Admin Processes 12 Factor App
- 75. • Codebase • Dependencies •Config • Backing services • Build, release, run • Processes • Port Binding • Concurrency • Disposability • Dev/Prod Parity • Logs • Admin Processes 12 Factor App
- 76. Admin tasks should berun in isolated processes
- 77. $ heroku runbash Running `bash` attached to terminal... up, run.1594 ~ $
- 78.
- 79. • Codebase • Dependencies •Config • Backing services • Build, release, run • Processes • Port Binding • Concurrency • Disposability • Dev/Prod Parity • Logs • Admin Processes 12 Factor App
- 80.
- 81. Create a bintray.comaccount1. set JDBC_DATABASE_URL=jdbc:postgres://…2. Measure your app’s boot time3. Click a Heroku button4. What next?
- 82.
- 83. Joe Kutner @codefinger JVM PlatformOwner (http://www.slideshare.net/jkutner/javaone-2015-12-factor-app) http://bit.ly/1PSRxcm