tezvyn:

Migrating a stateful monolith to PaaS

Source: interviewadvanced

WHAT IT TESTS: cloud-native refactoring strategy. OUTLINE: externalize state to backing services, make processes stateless and disposable, read config from the environment per Twelve-Factor. RED FLAG: a lift-and-shift that keeps local-disk state.

WHAT IT TESTS: applying Twelve-Factor principles to remove statefulness. ANSWER OUTLINE: find every place the app writes local state, sessions, uploads, caches, logs, and move each to a backing service: object storage for files, a database or cache for sessions, a queue for jobs, stdout for logs. Make processes stateless and disposable so any instance serves any request and scales horizontally, and externalize config to environment variables. RED FLAG: a lift-and-shift that preserves local-disk dependence and long-lived instances.

Read the original → interview

Get five bites like this every day.

Tezvyn delivers a daily feed of 60-second tech bites with quizzes to lock in what you learn.

Migrating a stateful monolith to PaaS · Tezvyn