Architecture

Architecture / InfoQ / 2 hours ago

Article: Enabling Evolutionary Architecture Through the Preservation of Change Locality

Why it matters — For engineers, boundary drift means that seemingly simple features (e.g., changing a delivery address) require cross-team coordination and deep system-wide knowledge, slowing delivery and increasing risk. The article offers practical sociotechnical strategies—redistributing mechanics, exposing essential policy, and rehearsing exception paths—to restore locality and keep changes proportional to their scope.

Architecture / Lobsters / 9 hours ago

Retries don't fix eventual consistency

Why it matters — Engineers building distributed systems often default to retries and dead-letter queues when dependent data hasn't arrived yet, creating unnecessary operational burden and ordering problems. Recognizing that missing data under eventual consistency is a valid system state—not an error—leads to simpler architectures where events wait for their prerequisites naturally.

Architecture / Cloudflare / 3 weeks ago

Introducing Meerkat: an experiment in global consensus

Why it matters — Engineers operating distributed systems across wide-area networks regularly face availability problems when leader-based consensus algorithms like Raft lose their leader to crashes or network degradation—Cloudflare itself has suffered multiple incidents from this. QuePaxa's leaderless, timeout-free design could offer a more resilient foundation for globally distributed control-plane state if it proves viable at production scale.

Architecture / Martin Fowler / 4 days ago

The Economic Benefit of Refactoring

Why it matters — Only one feed elseif tracks has carried this so far, so there is no independent corroboration yet. Read it as a single-source report.

Architecture / Netflix Technology / 2 weeks ago

Building Service Topology at Scale: Architecture, Challenges, and Lessons Learned

Architecture / Lobsters / 1 day ago

The First Idempotency Key

Why it matters — Engineers rely on idempotency keys daily to handle the fundamental distributed systems problem that exactly-once delivery is impossible and instead guarantee exactly-once processing through de-duplication. Understanding the pattern's history clarifies that Stripe named but did not invent the concept, and earlier implementations like Amazon EC2's ClientToken and Nottingham's POE draft predate it.

Architecture / InfoQ / 1 day ago

Cloudflare Introduces Meerkat for Strongly Consistent Global Coordination

Why it matters — For engineers operating multi-region systems, leader-based consensus like Raft creates availability gaps when a leader crashes or becomes unreachable, blocking writes until timeout-based failover completes. Meerkat's asynchronous approach eliminates that single point of failure, though the trade-off is one to three round trips per write decision, raising questions about whether performance remains competitive under normal conditions.

Architecture / Hugging Face / 3 days ago

GPU Management: Why Idle GPUs Are the New Grounded Aircraft

Architecture / Redis / 4 weeks ago

Cache layer architecture: a practical guide to speed & scale

Architecture / Redis / 1 week ago

5 agent architecture scenarios: assess MCP vs. A2A

Architecture / InfoQ / 3 days ago

Presentation: The Free-Lunch Guide to Idea Circularity

Architecture / InfoQ / 3 days ago

Presentation: Parting the Clouds: The Rise of Disaggregated Systems