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.

1. 12 Factor
App
Best Practices for Java
Deployment

2. You might not like what I have to say

3. Modern Java
Deployment

4. .war
Traditional Java Deployment

5. .jar
Modern Java Deployment

6. Make JAR
Not WAR

7. 2005 2015
WAR files JAR files
App Servers Microservices
Hot Deploy Continuous Deploy
Server in a closet Heroku/AWS/etc

8. Joe Kutner
@codefinger
JVM Platform Owner

9. 12 Factor App
a methodology
Scalability
Maintainability
Portability

10. Immutable
Ephemeral
Declarative
Automated

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. Use version
control

16. BAD

17. BAD
App #1 App #2

18. pom.xml
<project>
...
<modules>
<module>my-app</module>
<module>my-other-app</module>
</modules>
<project>

19. Submodules

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 on implicit
existence of system-wide
packages
Explicitly declare
and isolate
dependencies

22. Don’t check
JAR files
into Git

24. https://bintray.com/

25. Agent JARs

26. pom.xml
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-dependency-plugin</artifactId>
<version>2.6</version>
<executions>
<execution>
<id>copy-new-relic</id>
<phase>package</phase>
<goals>
<goal>copy-dependencies</goal>
</goals>
<configuration>
<includeGroupIds>com.newrelic.agent.java</includeGroupIds>
<includeArtifactIds>newrelic-agent</includeArtifactIds>
<stripVersion>true</stripVersion>
</configuration>
</execution>
</executions>
</plugin>

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 handles to 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 strictly separated
from code

31. Don’t check
passwords
into Git

33. Configuration belongs
in the environment,
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. application.conf
db.default.url=${DATABASE_URL}

36. Can you make your 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. application.conf
db.default.url=${DATABASE_URL}

40. • Codebase
• Dependencies
• Config
• Backing services
• Build, release, run
• Processes
• Port Binding
• Concurrency
• Disposability
• Dev/Prod Parity
• Logs
• Admin Processes
12 Factor App

41. build, release, run

42. $ mvn clean install
$ sbt stage
$ ./gradlew build
build

43. $ heroku deploy:jar -j myapp.war
$ mvn heroku:deploy
$ docker push ...
release

44. $ java -jar myapp.war
$ build/install/myapp/bin/myapp.bat
run
$ mvn jetty:run
$ service tomcat start
$ cp myapp.war TOMCAT_HOME/webapps/

45. $ git push heroku master
build,
release,
& run

46. DemoTime

47. • Codebase
• Dependencies
• Config
• Backing services
• Build, release, run
• Processes
• Port Binding
• Concurrency
• Disposability
• Dev/Prod Parity
• Logs
• Admin Processes
12 Factor App

48. Processes
should be
stateless

49. sticky sessions
😞

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
is completely self-contained
The web app exports HTTP
as a service by binding to a port

52. .war
Traditional Deployment

53. .jar
Modern Deployment

54. Dropwizard

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, I got this…
java.util.concurrent
RxJava
java.util.stream

57. Scale Up
Scale Out

58. web.1
web.2
worker.1 clock.1
Workload Diversity
NumberofProcesses
worker.2
worker.3

59. • Codebase
• Dependencies
• Config
• Backing services
• Build, release, run
• Processes
• Port Binding
• Concurrency
• Disposability
• Dev/Prod Parity
• Logs
• Admin Processes
12 Factor App

60. Graceful shutdown
Quick startup
Resilience to failure

61. Servers are not pets
Servers are cattle

62. Application Servers
are pets

63. Application Servers
are not
disposable

64. Microservices are
cattle

65. Microservices are
disposable

66. Easy to replace
Decoupled from
external infrastructure
Easy to modify

67. Microservices

68. • Codebase
• Dependencies
• Config
• Backing services
• Build, release, run
• Processes
• Port Binding
• Concurrency
• Disposability
• Dev/Prod Parity
• Logs
• Admin Processes
12 Factor App

69. dev stage prod= =

70. dev
sqlite
stage
mysql
prod
postgres
=
≠
=
≠

71. dev
sqlite
postgres
stage
mysql
postgres
prod
postgres
postgres
=
≠
=
=
≠
=

72. dev
tomcat
jetty
stage
tomcat
jetty
prod
jboss
jetty
=
≠
=
=
≠
=
.jar

73. disposability
reproducibility
parity

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 be run
in isolated processes

77. $ heroku run bash
Running `bash` attached to terminal... up, run.1594
~ $

78. web1
web2
web3
admin

79. • Codebase
• Dependencies
• Config
• Backing services
• Build, release, run
• Processes
• Port Binding
• Concurrency
• Disposability
• Dev/Prod Parity
• Logs
• Admin Processes
12 Factor App

80. http://12factor.net
http://jkutner.github.io

81. Create a bintray.com account1.
set JDBC_DATABASE_URL=jdbc:postgres://…2.
Measure your app’s boot time3.
Click a Heroku button4.
What next?

82. https://github.com/britter/spring-boot-heroku-demo

83. Joe Kutner
@codefinger
JVM Platform Owner
(http://www.slideshare.net/jkutner/javaone-2015-12-factor-app)
http://bit.ly/1PSRxcm