--- title: "Echoes" canonical: "https://current.tinyfish.ai/issue/6/echoes" publication: "TinyFish" publisher: "TinyFish" language: "en-US" guide: "https://current.tinyfish.ai/llms.txt" permalink: "https://current.tinyfish.ai/issue/6/echoes" issue: 6 section: "echoes" description: "Past infrastructure decisions echoing in today's production realities" authors: ["Nora Kaplan"] published: 2025-12-08 updated: 2025-12-04 articles: 18 --- # TinyFish > CURRENT is a journal about AI agents in production, for the engineering and product leaders who have to make them work. Drawing on experience building enterprise web agents, it explains why the demo succeeded and the deployment didn't, and what that means for choosing vendors, briefing the board, and avoiding mistakes others have already made. [Read on the website]() ## Issue 6 — Echoes Past infrastructure decisions echoing in today's production realities ### Historical Deep Dive - [When HTML Forked: The Compromise That Never Ended]() — By [Nora Kaplan]() · Published 2025-12-03 · Format: Infrastructure Inflections In February 1996, the HTML Editorial Review Board struck a deal: Netscape would remove blink tag from the specification if Microsoft removed marquee tag. Both companies agreed. Browsers kept supporting them anyway. ### One Echo This Week - [WebSocket Broke Every Assumption About Connections]() — Published 2025-12-03 December 2011: RFC 6455 standardized WebSocket. Developers celebrated real-time communication without polling hacks. Infrastructure teams got a problem that still hasn't resolved. ### Patterns Repeating Right Now Infrastructure doesn't evolve randomly. It follows patterns that repeat across decades, visible in every technology transition if you know where to look. The web you're building on today carries weight. Countless architectural decisions, each creating ripples that reach your production systems right now. Understanding these patterns changes what you build next. These six patterns show up everywhere: in your Kubernetes clusters, your cloud bills, your hiring struggles, your architecture debates. They're not historical curiosities. They're the infrastructure reality you're navigating today, echoing decisions made long before your systems existed. - **Complexity Always Gets Buried** — [Source]() — Published 2025-12-03 Tag: Abstraction Layers Kubernetes hid container orchestration. Platform engineering teams now hide Kubernetes. By 2026, 80% of large organizations will run internal developer platforms hiding the platforms that hide the infrastructure. Watch any technology long enough: someone builds an abstraction layer. Then someone abstracts that abstraction. The cycle never stops. - **The S-Curve Reveals Everything** — [Source]() — Published 2025-12-03 Tag: Adoption Curves Slow start, explosive middle, grinding plateau. Every technology follows this arc. Early gains feel effortless. Later improvements demand exponential effort for marginal returns. AI adoption in 2025 sits somewhere on that curve. The shape never lies about where you are in the cycle or what comes next. - **Complexity Compounds Faster Than Solutions** — [Source]() — Published 2025-12-03 Tag: Distributed Systems Add three nodes, get nine connections. Deploy microservices, coordination overhead explodes geometrically. The distributed monolith exists because coupling persists despite architectural intentions. Infrastructure drift becomes inevitable. Management overhead grows faster than the systems being managed. Always has, always will. - **Infrastructure Outpaces Human Learning** — [Source]() — Published 2025-12-03 Tag: Skills Gap Three point four million cybersecurity jobs sit unfilled globally. Hybrid clouds need expertise in both legacy and cloud systems simultaneously. Platform engineering emerged partly because skilled operators are scarce. Each technology wave amplifies the gap. Infrastructure evolves on Moore's Law. People don't. - **Centralize, Decentralize, Repeat** — [Source]() — Published 2025-12-03 Tag: Architecture Pendulum Mainframes to PCs to cloud to edge. Gartner predicts 75% of enterprise data at the edge by 2025, up from 10% in 2018. Each swing solves yesterday's problems while creating tomorrow's. Edge computing is just the latest decentralization wave. The pendulum never stops moving. - **Performance First, Bills Later** — [Source]() — Published 2025-12-03 Tag: Cost Optimization Build fast, discover costs afterward. Cloud spending hit $290 billion in 2023, growing 18% while organizations struggle to justify basic network upgrades. Infrastructure drifts toward poorly optimized states. The cycle repeats: optimize for performance, face cost pressure, re-architect, create new performance problems. Different decade, same pattern. ### Papers That Built Infrastructure - **CAP Theorem Proved the Impossible Triangle** — [Source]() — Published 2025-12-03 Brewer's 2000 conjecture, proven by Gilbert and Lynch in 2002, revealed what distributed systems builders already suspected: you cannot simultaneously guarantee consistency, availability, and partition tolerance. The theorem didn't create this constraint. It formalized an impossibility that was always there, forcing every database architect since to choose which guarantee to sacrifice. What did this change? Every eventual consistency decision in modern architecture accepts this proven impossibility as fundamental constraint. Where does this surface? NoSQL databases exist because CAP forced architects to choose availability over immediate consistency at scale. - **Fielding's Dissertation Documented the Web's Hidden Architecture** — [Source]() — Published 2025-12-03 Roy Fielding's 2000 dissertation extracted the architectural principles already embedded in HTTP and the web. While co-authoring HTTP 1.1, he recognized that constraints like statelessness and uniform interfaces weren't limitations but the source of the web's scalability. REST described what was working, not what should work. Today's API debates still argue over patterns he documented. What's the insight? The web scaled because of architectural constraints, and Fielding showed us which constraints actually mattered. Why does this echo? Every RESTful API inherits decisions made for browsers, whether those decisions fit the problem or not. - **MapReduce Made Distributed Processing Accessible** — [Source]() — Published 2025-12-03 Dean and Ghemawat's 2004 paper revealed how Google processed petabytes by hiding distributed systems complexity behind two functions: map and reduce. The abstraction made parallel processing accessible to programmers who didn't need to understand distributed systems internals. Hadoop emerged two years later, carrying these patterns into every data pipeline since. What's the breakthrough? Google was running 100,000 MapReduce jobs daily when they published production lessons, not theory. Where's the impact? Hadoop adopted these patterns wholesale, shaping how an entire generation processes large-scale data today. - **Bigtable Showed How to Store Petabytes** — [Source]() — Published 2025-12-03 Chang's 2006 paper documented how Google stored petabytes across thousands of commodity servers using a sparse, distributed, persistent sorted map. Already running in production since 2005 with over 60 Google products depending on it, Bigtable proved you could build flexible storage that handled both batch processing and real-time serving. Every NoSQL database since borrows from this architecture. What did this prove? Flexible schema design could scale to petabytes while serving both analytics and production traffic simultaneously. How does this echo? HBase, Cassandra, and Cloud Bigtable all trace their lineage directly to patterns documented here. ### Today's Debates Yesterday's Decisions - **HTTP Archive's 2024 Web Almanac on Protocol Persistence** — [Source]() — Published 2025-12-03 One in five pages still runs HTTP/1.1, twenty-seven years after its release. 1997's protocol decisions live in production today. - **Deloitte Measures the Developer Time Tax from Technical Debt** — [Source]() — Published 2025-12-03 Developers spend a third of their time managing architectural choices made before they arrived. Past decisions compound into present-day overhead. - **Academic Research on Shared Databases Blocking Microservices Migrations** — [Source]() — Published 2025-12-03 Monolithic-era database designs create the most persistent obstacles when organizations try to decompose systems. The schema decisions that won't let go. - **Kubernetes Survey Finds Interoperability Challenges Despite Growing Adoption** — [Source]() — Published 2025-12-03 Three-quarters of production environments struggle with orchestration across infrastructure built for pre-container assumptions. Old foundations, new coordination problems. - **AWS Compares GraphQL and REST API Design Philosophies** — [Source]() — Published 2025-12-03 REST's fixed endpoints and full-dataset returns pushed Facebook to build GraphQL in 2012. That solution now creates its own caching challenges. - **Red Hat on Kubernetes Patterns Responding to Infrastructure Limits** — [Source]() — Published 2025-12-03 Cloud-native architecture solves monolithic scalability constraints by accepting new complexity. Operational flexibility replaces the development simplicity that came before. ## Other sections in Issue 6 - [Daily Brief]() - [Market Pulse]() - [Foundations]() - [Practitioner's Corner]() - [Vision]() ## More - [Publication guide]() - [Issue archive]()