It's one thing for developers to write a Connect add-on. It's a whole different thing to run it in a production mode. When you consider both development and production, a series of questions emerges: - How do I reduce the cost and overhead of administering environments (servers)? - How can I build in scalability from the start? - How can I enable continuous deployment? The 12-factor application principles are often cited as the solution. Using the principles of 12-factor applications, it is much easier to go from rapid development iterations into production. And then to keep the pace of rapid iteration, even as each goes into production. From this talk, you will learn what the 12 factors are and how they can supercharge your Atlassian Connect add-on. Peter Van de Voorde, Community Developer, Atlassian

1. 12 ways to supercharge your
Connect add-on
PETER VAN DE VOORDE | DEVELOPER RELATIONS | ATLASSIAN | @PVDEVOOR

2. Source Flickr (d_t_vos)

3. I. Codebase
One codebase tracked in revision control, many deploys.

4. Source FotoDB.de (Nudeln)
II. Dependencies
Explicitly declare and isolate dependencies.

5. Source Flickr (Dennis Jarvis)
III. Config
Store config in the environment.

6. Source Photopin (Bill Ward's Brickpile)
IV. Backing Services
Treat backing services as attached resources.

7. Source: Flickr (kmardahl)
V. Build, Release, Run
Strictly separate build and run stages.

8. VI. Processes
Execute the app as one or more stateless processes.
Source: Flickr (archer10)

9. VII. Port Binding
Export services via port binding.
Source: Flickr (archer10)

10. Source: Flickr (br1dotcom)
VIII. Concurrency
Scale out via the process model.

11. Source: Wikimedia (i_yudai)
IX. Disposability
Maximize robustness with fast startup and graceful shutdown.

12. Source: Photopin (KaseyEriksen)
X. Dev/Prod Parity
Keep development, staging, and production as similar as possible.

13. Source: Photopin (RTCA NPS)
XI. Logs
Treat logs as event streams.

14. Source: Flickr (wuestenigel)
XII. Admin Processes
Run admin/management tasks as one-off processes.

15. Source: Photopin (MattusB)
Recap

16. I. Codebase
One codebase tracked in revision control, many
deploys.

17. I. Codebase
One codebase tracked in revision control, many
deploys.
II. Dependencies
Explicitly declare and isolate dependencies.

18. I. Codebase
One codebase tracked in revision control, many
deploys.
II. Dependencies
Explicitly declare and isolate dependencies.
III. Config
Store config in the environment.

19. IV. Backing Services
Treat backing services as attached resources.

20. IV. Backing Services
Treat backing services as attached resources.
V. Build, Release, Run
Strictly separate build and run stages.

21. IV. Backing Services
Treat backing services as attached resources.
V. Build, Release, Run
Strictly separate build and run stages.
VI. Processes
Execute the app as one or more stateless
processes.

22. VII. Port Binding
Export services via port binding.

23. VII. Port Binding
Export services via port binding.
VIII. Concurrency
Scale out via the process model.

24. VII. Port Binding
Export services via port binding.
VIII. Concurrency
Scale out via the process model.
IX. Disposability
Maximize robustness with fast startup and
graceful shutdown.

25. X. Dev/Prod Parity
Keep development, staging, and production as
similar as possible.

26. X. Dev/Prod Parity
Keep development, staging, and production as
similar as possible.
XI. Logs
Treat logs as event streams.

27. X. Dev/Prod Parity
Keep development, staging, and production as
similar as possible.
XI. Logs
Treat logs as event streams.
XII. Admin Processes
Run admin/management tasks as one-off
processes.

28. Thank you!
PETER VAN DE VOORDE | DEVELOPER RELATIONS | ATLASSIAN | @PVDEVOOR