Why not store uploads on local PaaS disk?
WHAT IT TESTS: statelessness and ephemeral storage. OUTLINE: PaaS instances are ephemeral and unshared, so local files vanish on restart and are invisible to peers; store uploads in object storage. RED FLAG: treating instance disk as durable or shared.
WHAT IT TESTS: understanding that PaaS instances are stateless and ephemeral. ANSWER OUTLINE: instances can be restarted, replaced, or scaled at any time, so local disk is wiped on each new container and is never shared between instances behind a load balancer; a file written on one node is missing on others and lost on redeploy. The standard pattern is to upload to a managed object store such as S3, GCS, or Azure Blob and persist only the key or URL. RED FLAG: assuming local disk is durable or shared.
Read the original → interview
- #object-storage
- #s3
- #stateless
- #paas
- #architecture
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.