Tag
state-management
- Oct 13, 2026 Shared State Without a Shared Heap Two platform runtimes cannot hold the same objects, so cross-platform state lives in an external store with subscription and persistence semantics that the framework must define itself. mobile computing
- Jun 10, 2026 Designing for Blast Radius in a Single Apply How state boundaries, replacement rules, and apply ordering determine how much infrastructure a failed run can take down, and what can be enforced before the call is made. cloud infrastructure
- Apr 20, 2026 State as a Mapping Between Addresses and Real Objects What a provisioning state file actually stores, why it is the tool's only durable record of identity, and how concurrent access corrupts that record. cloud infrastructure
- Jan 30, 2026 Count, for_each, and the Stability of Instance Addresses How a resource with a repetition argument becomes several state addresses, why index keys renumber on deletion while map keys do not, and what that costs at apply time. cloud infrastructure
- Dec 21, 2025 Merkle Trees as a Signature Scheme: One Key, Many One-Time Keys A hash-based signature is a one-time object, and a binary authentication tree is what turns a finite collection of them into a long-lived public key with logarithmic signatures. cryptography
- Aug 18, 2024 Provider Versions, Schema Changes, and State Migration How a provider upgrade can change the meaning of stored state, why schema versions exist per resource type, and what an upgrade path can and cannot fix. cloud infrastructure
- Jul 11, 2024 Importing Existing Resources into a Declarative Configuration What adoption actually writes into state, why a written resource block must match the object before the plan is clean, and where import cannot reach. cloud infrastructure
- Apr 28, 2024 Mirroring Widget State Into ARIA Attributes Without Drift Why every interactive custom widget keeps state in two places, which attributes the tree actually reads, and how a render boundary prevents the two copies from disagreeing. accessibility
- Jan 25, 2022 Saved Plans, State Serial, and Why Apply Must Be Pinned A saved plan is a reviewable artifact tied to one state snapshot. What it records, why apply rejects a stale one, and where the guarantee stops. devops