Menu

Containers die whenever; two hours of progress should not die with them
📰

Containers die whenever; two hours of progress should not die with them

DEV Community: kubernetes·dreamyman·2 days ago
#Q57BQ34U
#devtokubernetes#devto#dev#container#progress
Reading 0:00
15s threshold

Three posts in: tasks are isolated from each other, and the wait went from 45 seconds to a fraction of one. But one thing has not changed since the first post — progress still lives in the container's own memory .

That used to mean "a crash loses it". Now it is worse: containers in a warm pool are replaced as a matter of routine . Upgrades replace them, machine failures replace them, resource pressure reclaims them. They are consumables by design.

Which reframes the question: why would you let a consumable hold two hours of your work?

Write it somewhere else: the site blackboard, not the worker's head

Picture a construction site.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.