The 12 factor methodology is about 13 years old. How did it age in the cloud-native era? Do we need a 13th factor?. Tagged with cloudnative, kubernetes, operations, development.

Blobstation

Kiran Patel

Community Picks is a section on daily.dev where our community members share the most interesting and valuable content they've discovered online. From insightful articles to handy tools, every post is a gem curated by our dedicated coomunity. To contribute to Community Picks, you need to have at least 250 reputation points, ensuring that only active and trusted members can share their finds.

Community Picks

The 12 factor methodology, initiated by Heroku 13 years ago, still holds up for modern cloud-native applications. It covers topics such as codebase, dependencies, configuration, backing services, build-release-run stages, stateless processes, port binding, concurrency, disposability, dev/prod parity, logs, and admin processes. Additionally, forward and backward compatibility is important for smooth application deployments.

12 Factor: 13 years later

Factor 13: Forward and backward compatibility