Powered by OpenAIRE graph
Found an issue? Give us feedback
image/svg+xml art designer at PLoS, modified by Wikipedia users Nina, Beao, JakobVoss, and AnonMoos Open Access logo, converted into svg, designed by PLoS. This version with transparent background. http://commons.wikimedia.org/wiki/File:Open_Access_logo_PLoS_white.svg art designer at PLoS, modified by Wikipedia users Nina, Beao, JakobVoss, and AnonMoos http://www.plos.org/ ZENODOarrow_drop_down
image/svg+xml art designer at PLoS, modified by Wikipedia users Nina, Beao, JakobVoss, and AnonMoos Open Access logo, converted into svg, designed by PLoS. This version with transparent background. http://commons.wikimedia.org/wiki/File:Open_Access_logo_PLoS_white.svg art designer at PLoS, modified by Wikipedia users Nina, Beao, JakobVoss, and AnonMoos http://www.plos.org/
ZENODO
Preprint
Data sources: ZENODO
addClaim

The Declarative Illusion — Why Every System Becomes Imperative at Scale

The Declarative Illusion — Why Every System Becomes Imperative at Scale

Abstract

The term "declarative" has become a central selling point for modern infrastructure tools. Kubernetes, OpenTofu (Terraform), SQL, and countless other systems claim declarative models as a core feature. This paper argues that declarativity is not an inherent property of a system, but a function of its design relative to a bounded use case. Moreover, the recursive application of declarative procedures inevitably pushes systems toward imperativity, and attempts to maintain declarativity across expanding contexts destroy the very "easiness" that made them attractive.

Powered by OpenAIRE graph
Found an issue? Give us feedback