Tech • Architecture • Opinion
The Return of Monoliths
Microservices are complexity traps for 99% of teams. Why modular monoliths in Next.js/Turborepo are becoming the preferred architecture.
The Microservice Tax
Network latency, serialization costs, distributed tracing, eventual consistency. The list of problems you invite when you split your app is massive. For a team of 5, it's a productivity killer.
Modular Monoliths
We can have boundaries without network calls. Using tools like NX or Turborepo, we can enforce strict module boundaries (e.g. 'billing' cannot import 'auth' directly) while keeping everything in a single deployable unit.
Latest articles
View blog
Feb 12, 2025
The State of AI Agents in 2025
Moving beyond simple chatbots to autonomous agents that plan, execute, and verify. A look at the architectures defining the next wave of AI.
Feb 10, 2025
React Compiler: Goodbye useMemo?
React 19's optimizing compiler promises to automate memoization. I tested it on a large codebase to see if manual optimization is truly dead.
Feb 5, 2025
Next.js Middleware Mastery
Advanced patterns for using Edge Middleware to handle authentication, geolocation, and AB testing before the request hits your layout.