intermediate~2h

From 12-Factor to 15-Factor: Cloud-Native App Design

The original 12-Factor App methodology was written for the PaaS era. Running on Kubernetes surfaces three gaps the original list never had to cover — telemetry, authentication/authorization, and API-first design — and this module covers what each one actually demands of a service.

Learning objectives

  • Beginner: List the three factors that extend the original 12-Factor methodology and state, in one line each, what problem they solve.
  • Beginner: Explain why statelessness and externalized config (already covered by 12-Factor) remain prerequisites for the new three.
  • Intermediate: Design a service's telemetry surface — logs, metrics, traces — so an operator can diagnose it without attaching a debugger.
  • Intermediate: Decide where authentication belongs in a microservice (edge, sidecar, or application code) and justify the choice.
  • Advanced: Produce an API-first contract (OpenAPI spec) before writing a service's implementation and explain what that ordering buys a team.
  • Advanced: Audit an existing Spring Boot service against all 15 factors and identify which ones it violates.

This is a Pro chapter

Sign in, then upgrade to Pro or Power to unlock this and the full Spring Ecosystem Mastery library.

From 12-Factor to 15-Factor: Cloud-Native App Design

Next Step

Continue to Event-Driven Messaging with RabbitMQ →← Back to all Spring Cloud chapters