12 Ways to Supercharge Your Connect Add-on
0 likes5,115 views
The document outlines 12 key principles for enhancing connect add-ons, focusing on practices like managing a single codebase, isolating dependencies, and treating logs as event streams. Additional recommendations include maximizing disposability, ensuring development and production environments are similar, and separating build and run stages. The author emphasizes the importance of these best practices for robust application management.
More Related Content
Similar to 12 Ways to Supercharge Your Connect Add-on (20)
12 Ways to Supercharge Your Connect Add-on
- 1. 12 ways to supercharge your Connect add-on PETER VAN DE VOORDE | DEVELOPER RELATIONS | ATLASSIAN | @PVDEVOOR
- 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.
- 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