Rubber Band Architecture

Definitions

Rubber Band Architecture describes a software system design that stretches and deforms under pressure but snaps back rather than adapting permanently, exhibiting superficial flexibility without true resilience. The term is used critically to describe architectures that can handle temporary load increases or feature additions but tend to return to their problematic original state, accumulating technical debt and latent instabilities. Unlike truly elastic architectures that scale gracefully and maintain stability under varying loads, rubber band architectures give the illusion of handling change while actually becoming increasingly fragile with each stretch. Symptoms include services that degrade unpredictably under moderate load, quick fixes that temporarily resolve issues but introduce new failure modes, and systems where every new feature seems to break existing ones. The metaphor captures how these systems always feel like they are about to snap. The antidote is investing in genuine scalability patterns, proper observability, chaos engineering, and addressing root causes rather than applying temporary patches.
In plain English: A system held together by fragile workarounds and undocumented tricks — it works, but one wrong move could make it all snap apart like an overstretched rubber band.