12 Factor Snake

Transcript

1. The Twelve Factor Snake
2. I promise! Source: https://xkcd.com/365/
3. nabarun pal Infrastructure@Clarisights Python and Go loving polyglot Wears multiple hats in Kubernetes community @theonlynabarun
4. twelve factor application
5. 1. Declarative formats to setup automation 2. Clean contract and maximum portability 3. Suitable for deployment on modern cloud platforms 4. Minimizing divergence across deployments 5. Agile scaling without much changes to underlying infrastructure Goals
6. codebase One codebase tracked in revision control, many deploys
7. ➔ Code should always be version controlled ➔ All deploys of the app should have the same code ➔ Different versions of the code may exist
8. dependencies Explicitly declare and isolate dependencies
9. ➔ Declare dependencies in requirements.txt or Pipfile depending on your choice of tooling ➔ Achieve isolation using virtualenv or Pipenv
10. config Store config in the environment
11. <TODO: CODE SNIPPET FROM REPO> ➔ Code should always be version control ➔ All deploys of the app should have the same code
12. backing services Treat backend services as attached resources
13. ➔ The application should not care about where external resources like databases, cache are running ➔ The application should just care about the correct configuration provided to it
14. build, release, run Strictly separate build and run stages
15. ➔ Isolation of build, release and run stages ➔ Releases should be unique and immutable
16. processes Execute the app as one or more stateless processes
17. ➔ Processes should not share state amongst themselves ➔ They should be completely stateless ➔ Any required state needs to be in backing databases
18. port binding Export services via port binding
19. ➔ Publish app as service through ports ➔ Self contained and doesn’t need runtime injection of web servers ➔ One application can act as a backing service for another app through URIs
20. concurrency Scale out via the process model
21. ➔ Processes are first class citizens ➔ Workloads should be able scale across machines ➔ NEVER try to do process management yourself - DELEGATE Source: https://12factor.net/concurrency
22. disposability Maximize robustness with fast startup and graceful shutdown
23. ➔ Processes should be destroyable at will ➔ Minimal startup time ➔ Graceful shutdown on termination signal ➔ Functionality should be idempotent
24. dev/prod parity Keep development, staging, and production as similar as possible
25. ➔ Try to bridge gaps in workflow ➔ Development environment and deployments should be as similar as possible ➔ Use same services in all environments
26. logs Treat logs as event streams
27. ➔ Logs are are chronological event streams ➔ Must be written unbuffered to stdout ➔ Log shippers are responsible to collect ➔ Ship to warehouses like Elasticsearch for slicing and dicing
28. admin processes Run admin/management tasks as one-off processes
29. $ createdb todo $ psql todo < schema/schema.sql --- $ python manage.py migrate ➔ Ad-hoc tasks like database migrations should be run as a separate job ➔ The runtime environment should be same as the main process
30. https://github.com/palnabarun/12factor-todo 12factor.net
31. Questions? Put a picture here hey@naba.run @theonlynabarun https://naba.run