5 posts
#architecture
Architecture posts with a bias toward simple systems. Why many teams move from microservices back to a modular monolith, how to choose between RabbitMQ, Redis Streams and Yandex Message Queue for background work, and where HTMX holds up in production. Two opinion pieces argue for boring tech like Postgres, nginx and PHP, and against monorepos for small teams.
Useful before a rewrite or a new project, while changing course is still cheap. Start with the boring tech piece. If you already run microservices and feel the pain, the modular monolith post is the one to read.
Related service: Web application development
(01)
From monolith to modular monolith — when to skip microservices
Microservices were the default architectural answer for a decade. In 2026 most teams that adopted them are walking back. The modular monolith is a saner middle ground for teams of 5-50 engineers.
→
(02)
Task queues: RabbitMQ vs Redis Streams vs Yandex Message Queue
Three common ways to separate "accept request" from "do the work" in Russian projects in 2026. Practical differences, what to pick for the load and for the team.
→
(03)
HTMX in production: where it works and where it falls apart
HTMX promises SPA without SPA: attributes on HTML, server returns HTML fragments. Three production projects later — here is where it really is simpler and where it hit the wall.
→
(04)
The case against monorepos for small teams
Turborepo and Nx made monorepos easy. That doesn't mean small teams should adopt one. Polyrepo is fine for 2-5 devs.
→
(05)
The case for boring tech in 2026
Every framework promises 10x velocity. Most teams ship faster on Postgres, nginx and PHP than on the framework of the month.
→