--- title: "Echoes" canonical: "https://current.tinyfish.ai/issue/50/echoes" publication: "TinyFish" publisher: "TinyFish" language: "en-US" guide: "https://current.tinyfish.ai/llms.txt" permalink: "https://current.tinyfish.ai/issue/50/echoes" issue: 50 section: "echoes" description: "Past infrastructure decisions echoing in today's production realities" authors: ["Sable Whitford","Sevda Polat"] published: 2026-10-12 updated: 2026-10-09 articles: 14 --- # TinyFish > A journal for living in the agentic age [Read on the website]() ## Issue 50 — Echoes Past infrastructure decisions echoing in today's production realities ### Transaction Boundary History - [What Compensation Actually Meant]() — By [Sable Whitford]() · Published 2026-10-08 · Format: Historical Parallels In 1987, two researchers wrote down something database operators already lived with: an operation that spans multiple systems can't hold everything still until it finishes. Their answer, the saga, came with a condition attached. Before any step was allowed to commit, the system had to already know how to walk that step back. Compensation was the price of decomposing a transaction into independent pieces, and you paid it up front. Nearly four decades later, agents run multi-step operations across services they don't control, with all of the flexibility and none of the condition. ### Compensating Transactions Explained - [You Can't Undo a Committed Act]() — By [Sable Whitford]() · Published 2026-10-08 A flight booked, a hotel confirmed, then the car rental fails. The customer wants the whole trip canceled. But the hotel already committed that reservation — allocated inventory, sent a confirmation email. You can't reach into their system and roll it back. You don't have the authority, and even if you did, the confirmation already went out. What you *can* do is send a new request: cancel the reservation. That cancellation is its own transaction, with its own consequences — a fee, a refund policy, a record that says *booked then canceled*, not *nothing happened*. ### Saga Practitioner Interview - [A Saga Pattern Survivor on the Third Path Nobody Drew on the Architecture Diagram]() — Published 2026-10-08 *Dex Rollback spent three years as a distributed systems architect at a major e-commerce platform during the great monolith decomposition of the mid-2010s. He now runs an independent consulting practice called Compensating Actions LLC, which helps organizations manage the operational fallout of distributed transaction patterns. We spoke over video call from what he described as "the room where I keep the whiteboards I should have burned." Neither Dex nor his impeccably named consultancy exist outside this conversation, but the problems he describes are painfully real.* ### Inside and Across Boundaries - [All or Nothing]() — By [Sable Whitford]() · Published 2026-10-08 · Format: Inside and Across Boundaries For decades, database transactions gave engineers a reliable deal: write the logic, trust the commit, and if something fails, the system handles it. The ACID contract, named in 1983 and built toward for a decade before that, made half-done impossible inside a single system. Reservations, payroll, accounting all sit on top of it. Then the boundary moved. - [The Promise That Stopped at the Wire]() — By [Sable Whitford]() · Published 2026-10-08 · Format: Inside and Across Boundaries The first time an application has to coordinate work across two systems, the ACID guarantee hits a wall. Two-phase commit tried to push it across the network and buckled under real conditions. Sagas replaced it with something weaker and more honest: not rollback but compensation, new actions that approximate an undo without erasing anything. Agents inherit that world, calling APIs across boundaries that share no transaction manager. ### Further Reading - **The Transaction Concept: Virtues and Limitations (Gray, 1981)** — [Source]() — Published 2026-10-08 Where ACID got its name. Gray's legal-contract analogy for compensation turns out to age remarkably well. - **Sagas (Garcia-Molina and Salem, 1987)** — [Source]() — Published 2026-10-08 The paper that broke long transactions into chains of compensable steps. Now the default pattern in microservices. - **Eventually Consistent (Vogels, 2008)** — [Source]() — Published 2026-10-08 Amazon's CTO made the case for tolerating temporary inconsistency in distributed systems. Shaped a generation of architecture. - **SagaLLM: Transaction Guarantees for Multi-Agent LLM Planning (Chang and Geng, 2025)** — [Source]() — Published 2026-10-08 A VLDB paper that takes the 1987 saga pattern and applies it to multi-agent coordination and rollback. - **Agentic Transaction: Towards ACID-Compliant Agent Systems (Sun, Wang, and Li, 2026)** — [Source]() — Published 2026-10-08 A preprint that asks what ACID properties mean when the executor is an autonomous agent, not a database. ### Past Articles - [The Same Absence, Learned]() — By [Sevda Polat]() · Published 2026-10-01 · Format: Two Eras of Guessing Vision models can now read a screenshot and try to work out which elements are clickable, what a button does, where to type. It is the task screen readers faced for decades, attempted with unrecognizably different machinery. On real desktop work, success rates sit near 5%, and when these models miss, there is no rule to open and no set of conditions to enumerate. - [The Heuristics of Last Resort]() — By [Sevda Polat]() · Published 2026-10-01 · Format: Two Eras of Guessing When a web interface doesn't declare what its elements are, a screen reader has to guess. Browsers have spent two decades maintaining hand-written rules that infer meaning from indirect evidence: click handlers, styling, proximity. The rules were ingenious and fragile. A declarative vocabulary arrived to make them unnecessary, and a third of the web's form fields still don't use it. - [Screen Readers Got There First]() — By [Sevda Polat]() · Published 2026-10-01 · Format: The Interpretability Gap Screen readers have spent thirty years extracting structure from pages built for sighted people with mice. Standards bodies, lawsuits, and decades of pressure on developers eventually moved the needle more than better parsing did. Web agents have arrived at the same gap with none of that behind them. After thirty years of coordinated effort, 95.9% of top homepages still fail basic automated checks. - [When the Combinations Outgrew the Room]() — By [Sable Whitford]() · Published 2026-09-24 · Format: Parallel Failure Modes After deregulation, American Airlines carried over 500,000 fares in its reservation system. Every rule made sense on its own. But nobody could predict what the system would do when you changed one, because the interactions between fare classes, routing constraints, and capacity controls across a flight network had outgrown any person's ability to hold them. The fix wasn't better rules. It was a statistical layer that absorbed combinations no human could work through by hand. A different kind of maintenance failure than the one next door, with a similar ending. ## Other sections in Issue 50 - [Daily Brief]() - [Market Pulse]() - [Foundations]() - [Practitioner's Corner]() - [Vision]() ## More - [Publication guide]() - [Issue archive]()