12 Factor App: Best Practices for JVM Deployment
•
30 likes•11,766 views
Twelve Factor apps are built for agility and rapid deployment. They enable continuous delivery and reduce the time and cost for new developers to join a project. At the same time, they are architected to exploit the principles of modern cloud platforms while permitting maximum portability between them. Finally, they can scale up without significant changes to tooling, architecture or development practices. In this talk, you’ll learn the principles and best practices espoused by the Twelve Factor app. We’ll discuss how to structure your code, manage dependencies, store configuration, run admin tasks, capture log files, and more. You’ll learn how modern Java deployments can benefit
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (14)
Similar to 12 Factor App: Best Practices for JVM Deployment
Similar to 12 Factor App: Best Practices for JVM Deployment (20)
More from Joe Kutner
More from Joe Kutner (20)
Recently uploaded
Recently uploaded (20)
12 Factor App: Best Practices for JVM Deployment
- 1. 12 Factor App Best Practices for JVM Deployment
- 2. 12 Factor App Best Practices for JVM Deployment Java doesn’t suck when you do things this way
- 4. Java Servlet API 2.2 includes one new feature so significant it may change the way the Web works. That feature: Web applications. - Javaworld.com, 1999 “ ”
- 5. With Web apps, the entire application can be contained in a single archive file and deployed by placing the file into a specific directory. - Javaworld.com, 1999 “ ”
- 10. Joe Kutner @codefinger JVM Langs Owner @Heroku Joe Kutner
- 11. 12 Factor App a methodology Scalability Maintainability Portability
- 12. The 12 Factors • Codebase • Dependencies • Config • Backing services • Build, release, run • Processes • Port binding • Concurrency • Disposability • Dev/prod parity • Logs • Admin processes
- 13. The 12 Factors • Codebase • Dependencies • Config • Backing services • Build, release, run • Processes • Port binding • Concurrency • Disposability • Dev/prod parity • Logs • Admin processes
- 14. Graceful shutdown Quick startup Resilience to failure | Disposability |
- 16. Application Servers are not disposable | Disposability |
- 17. | Disposability | Microservices are disposable
- 19. Bootable ➤ Disposable | Disposability |
- 20. The 12 Factors • Codebase • Dependencies • Config • Backing services • Build, release, run • Processes • Port binding • Concurrency • Disposability • Dev/prod parity • Logs • Admin processes
- 21. dev sqlite postgres stage mysql postgres prod postgres postgres = ≠ = = ≠ = | Disposable | Parity |
- 24. | Disposable | Parity | dev jetty {} stage tomcat {} prod jboss {} = ≠ = = ≠ =
- 27. Reproducible ➤ Parity | Disposable | Parity |
- 28. Reproducible ➤ Disposable | Disposable | Parity |
- 29. The 12 Factors • Codebase • Dependencies • Config • Backing services • Build, release, run • Processes • Port binding • Concurrency • Disposability • Dev/prod parity • Logs • Admin processes
- 30. Configuration belongs in the environment, not in the application Configuration should be strictly separated from code | Disposable | Parity | Config |
- 31. Linux Tomcat WAR server.xml context.xml web.xml /etc/... | Disposable | Parity | Config |
- 32. Environment Java Application PATH DATABASE_URL AWS_ACCESS_TOKEN JAVA_OPTS | Disposable | Parity | Config |
- 33. Containerless ➤ Separation | Disposable | Parity | Config |
- 34. Containerless ➤ Parity | Disposable | Parity | Config |
- 35. Containerless ➤ Disposable | Disposable | Parity | Config |
- 36. Containerless ➤ 12 Factor App | Disposable | Parity | Config |
- 37. Containerless Containerless Containerless | Disposable | Parity | Config |
- 38. The container is dead Long live the container Docker Heroku Docker+Heroku Application Server Servlet Container
- 39. Docker
- 41. Host OS App App App App Docker Containers Container Container Container Container Docker Engine
- 42. App App App App Host OS Dyno Dyno Dyno Dyno Heroku Dynos Heroku
- 43. App App App App Host OS Dyno Dyno Dyno Dyno Heroku Dynos HerokuSlug
- 44. Host OS App App App App Docker Containers Container Container Container Container Docker EngineImage
- 45. Dockerize!
- 46. FROM heroku/cedar:14 ... RUN /opt/heroku/bin/setup.sh /opt/heroku ... ENTRYPOINT /opt/heroku/bin/run.sh Dockerfile https://github.com/jkutner/heroku-java-docker REPRODUCIBLE Base Image ➤ Install Java ➤ Run App ➤
- 47. web: java -cp target/app.jar com.foo.Main Procfile https://github.com/jkutner/heroku-java-docker BOOTABLE
- 48. @Configuration @EnableAutoConfiguration @ComponentScan public class Main { public static void main(String[] args) { SpringApplication.run(Main.class, args); } } CONTAINERLESS
- 49. import org.eclipse.jetty.server.Server; import org.eclipse.jetty.servlet.*; public class Main { public static void main(String[] args) throws Exception { Server server = new Server(); ServletContextHandler context = new ServletContextHandler( ServletContextHandler.SESSIONS); context.setContextPath("/"); server.setHandler(context); context.addServlet(new ServletHolder(new App()), "/*"); server.start(); server.join(); } }
- 50. (defn -main [& [port]] (jetty/run-jetty (site #'app) {:port port :join? false}))
- 51. // Play example does not require any code
- 52. Dropwizard
- 53. Demo…
- 54. Host OS Docker EngineImage $ docker build ...
- 55. Host OS Docker EngineImage App Container $ docker run ... $ docker build ...
- 56. Host OS App Container Docker EngineImage App Container App App Container Container $ docker run ... $ docker build ... $ docker run ...
- 57. Host OS Docker Engine $ docker run ... $ docker build ... $ docker run ...
- 58. The 12 Factors • Codebase • Dependencies • Config • Backing services • Build, release, run • Processes • Port binding • Concurrency • Disposability • Dev/prod parity • Logs • Admin processes
- 59. | Disposable | Parity | Config | Admin | Admin tasks should be run in isolated processes
- 60. web1 web2 web3 admin | Disposable | Parity | Config | Admin |
- 61. The 12 Factors • Codebase • Dependencies • Config • Backing services • Build, release, run • Processes • Port binding • Concurrency • Disposability • Dev/prod parity • Logs • Admin processes
- 62. | Disposable | Parity | Config | Admin | Concurrency | Scale Up AND Scale Out
- 63. | Disposable | Parity | Config | Admin | Concurrency | web.1 web.2 worker.1 clock.1 Workload Diversity NumberofProcesses worker.2 worker.3
- 64. TAKE AWAYS!
- 65. • Install the JDK • Clone the SCM repo • Run the app 1) Three Steps to Setup
- 66. • Get a stopwatch • Time your app’s startup • Get it under 30 seconds 2) Make Startup Quick
- 67. • Provision a new environment, deploy the app, handle requests 3) Deploy in One Step
- 69. Joe Kutner @codefinger JVM Languages Owner @Heroku