18 articles found
Early microservices adoption imposes a hidden architectural tax that small teams can’t afford. Real data shows monoliths outperform microservices for teams under 10 developers, and even Amazon is reversing course.
The gap between microservices theory and reality leaves teams flying blind when changes ripple across distributed codebases. Here’s why even the best tooling fails, and what actually works.
A provocative deep-dive into the radical theory that all software architectures derive from five elementary geometries, and what that means for the future of system design.
Analyzing whether offset/limit pagination introduces UI-driven accidental complexity into core business interfaces, and how to refactor without compromising architectural boundaries.
Exploring the architectural patterns and hard trade-offs in scaling large language models to understand and generate code across massive, multi-repository codebases, and why most teams are solving the wrong problem.
The controversial practice of storing files directly in SQL databases isn’t the cardinal sin developers claim. New research reveals when database storage actually beats traditional file systems, and why the ‘best practice’ might be wrong.
An in-depth analysis of Twilio Segment’s controversial decision to abandon microservices for a monolith, exploring how 140+ services became a distributed nightmare and what the reversal taught the industry about architectural dogma.
Anthropic’s code execution pattern slashes AI agent token usage by 98.7% by having models write orchestrating code instead of direct tool calls, potentially enabling complex agents to run on consumer hardware with significant privacy benefits.
The collision of AI code generation and formal verification is rewriting the economics of reliable systems. As LLMs automate proof scripts, the question isn’t whether to verify, but how quickly you can adapt.
How complex system designs create barriers for junior engineers entering the field, exacerbating hiring challenges
A no-BS breakdown of three architectural heavyweights fighting for your next project’s soul
When rapid iteration kills documentation, testing, and system design, is extreme agile sustainable progress or professional malpractice?
Navigating cross-module communication in hexagonal monoliths without descending into dependency chaos
The arc42 team’s alternative quality model challenges decades of software quality dogma with 8 pragmatic attributes that might actually get used.
As LLMs spew unread code into production, teams face a new kind of technical debt where systems work but no human understands them.
Widespread AI coding assistant adoption is creating subtle but dangerous erosion of code quality, architectural consistency, and long-term maintainability.
Generative coding tools boost velocity while quietly eroding software architecture, creating monoliths faster than ever before. The data reveals a paradox: more code, more technical debt.
How API-first principles backfire when developers forget who actually uses their interfaces
