The Twelve-Factor App

 From wikipedia:

The Twelve-Factor App methodology is a methodology for building software-as-a-service applications. These best practices are designed to enable applications to be built with portability and resilience when deployed to the web.

https://12factor.net/

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

II. Dependencies
Explicitly declare and isolate dependencies

III. Config
Store config in the environment

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

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

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

 

Event Storming Rainbow

When trying to create a methodology/paradigm, but everybody starts changing colors.

Event Storming, a rainbow of post-it notes.

https://kalele.io/symbolsicons-for-event-storming/

https://github.com/wwerner/event-storming-cheatsheet

https://leanpub.com/introducing_eventstorming

https://eventnotes.io/pdf/cheatsheet-big-picture-exploration.pdf

https://developer.ibm.com/technologies/java/tutorials/reactive-in-practice-1/