The document discusses the 12 Factor App methodology for building cloud-native applications. It provides three stories that show how the 12 factors can be applied: 1) Containerizing a legacy application to make it cloud-native, 2) Using serverless computing and how the 12 factors still apply, and 3) Open sourcing a SaaS product using the GitLab model. In each story, the 12 factors are listed and it's explained how they relate to the cloud-native approaches and best practices discussed. The document concludes that the 12 factors provide good guidance but should not limit developers' creativity in building cloud applications.

1. 12 Factor Apps - the steps between using the
cloud and being cloud native
Wojciech Urbański

2. 2
At a glance
●
●
●
●
●
●
●
●
●
●
Wojciech Urbański CodiLime

3. Cloud is (not)
just someone else’s computer...

4. 4
“Using cloud” vs “using cloud effectively”
●
●
●
●
●
●
Cloud-enabled
Cloud-native

5. 5
Creating cloud-native applications
12 Factor Apps
● https://12factor.net
●
●
Main assumptions
● declarative formats for setting up automation
● clean contract with the underlying operating system maximum portability
● deployment cloud platforms
● minimize divergence continuous deployment
● scale up

6. 6
The Twelve Factors
1. Codebase
2. Dependencies
3. Config
4. Backing services
5. Build, release, run
6. Processes
7. Port binding
8. Concurrency
9. Disposability
10. Dev/prod parity
11. Logs
12. Admin processes

7. Become cloud-native through examples: 3 cloud stories.
Where theory meets practice

8. Containerizing a legacy application
Cloud is for containers after all, right?

9. 9
Containerizing a legacy application
Overview
● using containers
●
●
Problems
●
●
Solution (?)
●
all the processes single container

10. 10
Monolithic containers (sic!)
Issues
● Multiple processes
● separate logging facilities
● services available
locally
● stateful
● Horizontal scalability creates multiple unrequired
resources
Application container
supervisord
/var/log/...
application
dependency
worker
Application port (tcp/8080)

11. 11
Cloud-native
● Separate, mostly stateless processes
● platform
● backing services configuration
variables
● port bindings
● scaled out creating new instances
● backing services
● External logging
Cloud-native application architecture
Container runtime platform
Data storage
State storage
Frontend
(stateless)
Logging facility
Workers (stateless)

12. 12
Story 1: The Twelve Factors
1. Codebase
2. Dependencies
3. Config
4. Backing services
5. Build, release, run
6. Processes
7. Port binding
8. Concurrency
9. Disposability
10. Dev/prod parity
11. Logs
12. Admin processes

13. Is serverless the new definition
of cloud-native?

14. 14
Does serverless obsolete 12 Factor Apps?
Overview
●
●
●
How do 12 Factors apply here?
●
○ codebase dependencies environment parity
○ backing services config variables
●

15. 15
Story 2: The Twelve Factors
1. Codebase
2. Dependencies
3. Config
4. Backing services
5. Build, release, run
6. Processes
7. Port binding
8. Concurrency
9. Disposability
10. Dev/prod parity
11. Logs
12. Admin processes

16. Imagine the consequences
of your code being published to GitHub...

17. Open Source your SaaS -
based on the case of GitLab

18. 18
Open Source your SaaS
Why?
●
●
●
Problems
●
●
●
Solution
●
● Eat your own dog food!
●

19. 19
Open Core model - a case of GitLab
Open Core
●
GitLab
●
● multiple services a single codebase
●
● installation packages containers + helm charts
How do 12 Factors apply here?
●
● Applying best practices to CI/CD processes

20. 20
Story 3: The Twelve Factors
1. Codebase
2. Dependencies
3. Config
4. Backing services
5. Build, release, run
6. Processes
7. Port binding
8. Concurrency
9. Disposability
10. Dev/prod parity
11. Logs
12. Admin processes

21. But they are really good assumptions written by very smart people!
The Twelve Factors
are just written assumptions.

22. Tools and manifests are there to help you, not to bind you!
Focus on what you’re creating.

23. Thank you
SDN & NFV Cloud-native & Multi cloud Software Engineering UX / UI DevOps