--- title: "Echoes" canonical: "https://current.tinyfish.ai/issue/10/echoes" publication: "TinyFish" publisher: "TinyFish" language: "en-US" guide: "https://current.tinyfish.ai/llms.txt" permalink: "https://current.tinyfish.ai/issue/10/echoes" issue: 10 section: "echoes" description: "Past infrastructure decisions echoing in today's production realities" authors: ["Rina Takahashi"] published: 2026-01-05 updated: 2025-12-31 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 10 — Echoes Past infrastructure decisions echoing in today's production realities ### Historical Deep Dive - [How TCP Saved the Internet and Complicated Everything After]() — By [Rina Takahashi]() · Published 2025-12-31 · Format: Infrastructure Inflections Spin up a few thousand concurrent browser sessions and you'll hit a wall that feels arbitrary: ports exhaust, connections pile up in limbo, your infrastructure can't establish new sessions even though bandwidth looks fine. The operational puzzle isn't resource limits—it's something deeper. ### One Echo This Week - [When Schema Freedom Became Maintenance Prison]() — Published 2025-12-31 MongoDB and Redis arrived in 2009 promising escape from SQL's rigid schemas. Web 2.0 companies drowning in data grabbed the lifeline. No more schema migrations. No more JOIN complexity. Just store JSON and scale horizontally forever. ### Patterns Repeating Right Now The patterns playing out in your production systems have played out before. Mainframes to microservices, data centers to distributed clusters. Same fundamental dynamics, different velocity. Adoption cycles that took decades now compress into months. Complexity that accumulated gradually explodes overnight. The infrastructure phase changes keep happening faster. You're living through one right now. Teams coordinate through structures built for different scale. Workloads migrate to new compute layers. Configuration surfaces multiply faster than governance can track. These aren't predictions. They're observable in production today, echoing transitions that happened before at different speeds. - **Coordination Breaks Before Systems Do** — [Source]() — Published 2025-12-31 Tag: Team Growth At two hundred engineers, pull requests queue for days. Features need five conversations before shipping. The systems still work. The organization doesn't. You're not building too slowly. You're coordinating through structures designed for twenty people. - **Each Generation Reaches Scale Faster** — [Source]() — Published 2025-12-31 Tag: Adoption Velocity Personal computers needed sixteen years to reach mainstream adoption. Internet took seven. Smartphones, five. ChatGPT hit one hundred million users in two months. The pattern holds across every infrastructure generation: penetration velocity keeps accelerating. - **Inference Workloads Overtook Training Compute** — [Source]() — Published 2025-12-31 Tag: Compute Distribution In 2023, inference consumed one-third of AI compute. Now it's two-thirds. Training stays concentrated in massive clusters. Inference fragments across specialized hardware everywhere. Watch where the actual computational work migrates during technology maturation. - **Early Architecture Choices Echo for Years** — [Source]() — Published 2025-12-31 Tag: Service Boundaries Service boundaries drawn at twenty engineers still constrain teams at two hundred. Components that map cleanly to single teams scale smoothly. Those that don't require cross-team negotiation for every deployment. Your earliest architecture decisions determine growth capacity long after you've forgotten making them. - **Distribution Multiplies Configuration Risk Exponentially** — [Source]() — Published 2025-12-31 Tag: Configuration Surface Kubernetes and service meshes expand configuration surface area across clusters. One RBAC mistake opens backdoors everywhere. A single overlooked network policy cascades into system-wide incidents. Distribution transforms simple configuration errors into infrastructure-wide failures. - **Cloud-Native Architecture Intensifies Cost Pressure** — [Source]() — Published 2025-12-31 Tag: Cost Dynamics Infrastructure-as-code makes spinning up resources trivial. Cloud-native layers add complexity monoliths never faced. Highly dynamic environments become harder to meter accurately. As adoption grows, cost management shifts from afterthought to primary operational concern. ### Papers That Built Infrastructure - **MapReduce Made Distributed Computing Accessible to Ordinary Programmers** — [Source]() — Published 2025-12-31 Jeffrey Dean and Sanjay Ghemawat's 2004 paper automated parallelization, fault tolerance, and scheduling across thousands of machines. Programmers wrote simple map and reduce functions; the system handled distribution. By 2006, Google processed twenty petabytes daily through 100,000 MapReduce jobs. Hadoop, Spark, and modern batch processing descended directly from this model. How did this reshape infrastructure? Simple programs now scale across thousands of machines because MapReduce hid distributed complexity behind two functions. Where do you see this pattern? Cloud-native development inherited MapReduce's core idea: hide distribution behind simple interfaces developers already understand. - **CAP Theorem Formalized the Impossible Trade-offs in Distributed Systems** — [Source]() — Published 2025-12-31 Eric Brewer conjectured in 2000 what Gilbert and Lynch proved in 2002: distributed systems cannot simultaneously guarantee consistency, availability, and partition tolerance. Pick two. Every NoSQL database since has been a choice about which property to sacrifice. MongoDB chose consistency. Cassandra chose availability. Both accepted partition tolerance as inevitable. When does this hit production? Your database serves stale data or goes down during network partitions because CAP's constraints are physics, not bugs. How does this change decisions? Database evaluation becomes simpler once you recognize MongoDB versus Cassandra reflects fundamental trade-offs, not marketing claims. - **REST Was Designed for Hypermedia, Became the API Standard** — [Source]() — Published 2025-12-31 Roy Fielding's 2000 dissertation described architectural constraints for distributed hypermedia systems while co-authoring HTTP specifications. Mid-2000s developers, desperate for SOAP alternatives, repurposed REST for web APIs. Fielding never intended this. Every stateless API inherits constraints designed for browsers navigating linked documents, not microservices exchanging JSON. Where's the historical irony? REST optimized hypermedia navigation through links, but powers stateless request-response APIs that ignore hypermedia completely. Why do these constraints feel odd? Statelessness and uniform interfaces were optimized for web browsing, not the microservices you're actually building. - **Paxos Provided the First Correct Consensus Protocol for Distributed Systems** — [Source]() — Published 2025-12-31 Leslie Lamport discovered Paxos in the late 1980s. Reviewers found his parliament analogy too obscure for eight years until 1998 publication. The algorithm now powers Google Chubby, Spanner, and Megastore; Microsoft Autopilot; Amazon DynamoDB; Cassandra transactions. Distributed consensus became possible because Lamport proved correctness mathematically. What does Paxos actually enable? Leader election, configuration management, transaction coordination—any distributed agreement despite failures—relies on Paxos or its descendants. Why do consensus systems hang? Paxos sacrifices liveness for correctness during partitions. That apparent freeze is the system being mathematically correct. ### Today's Debates Yesterday's Decisions - **AI Workloads Collide With Pre-Pandemic Cloud Architecture** — [Source]() — Published 2025-12-31 Multicloud strategies from 2019 assumed web traffic patterns. AI's compute hunger exposes those assumptions daily. - **Database Architecture's Eternal Return: Stonebraker and Pavlo Trace Patterns** — [Source]() — Published 2025-12-31 MIT and Carnegie Mellon professors map how 1960s text search engines prefigured today's vector databases. - **Microservices' 2010s Promise Created Today's API Management Crisis** — [Source]() — Published 2025-12-31 Netflix and Amazon's architectural wins spawned API sprawl. Ninety-three percent of teams still struggle with collaboration. - **REST's Twenty-Year Legacy Constrains Event-Driven Architecture** — [Source]() — Published 2025-12-31 Fielding's 2000 dissertation solved request-response elegantly. Streaming data reveals what REST never anticipated. - **Serverless Cold Starts: Consequence of Abstracting Infrastructure Away** — [Source]() — Published 2025-12-31 The journey from bare metal through containers built initialization latency into serverless. Physics remains undefeated. - **Edge Computing Rediscovers CDN-Era Distribution Challenges** — [Source]() — Published 2025-12-31 Pushing compute to disconnected devices resurrects problems CDN architects solved differently. Reliable connectivity remains aspirational. ## Other sections in Issue 10 - [Daily Brief]() - [Market Pulse]() - [Foundations]() - [Practitioner's Corner]() - [Vision]() ## More - [Publication guide]() - [Issue archive]()