Architecture

Your system has 500 users and also has 20 microservices, including the gauntlet of Kubernetes, a message broker, distributed tracing, multiple different databases, and a pretty dashboard that probably nobody looks at. Someone will ask the question: why is this so complicated for 500 users? And usually the answer is, “Well, we’re building for scale.” No. No, you’re not. You’re building for scale you don’t have yet. That’s a lot of extra complexity. Scaling software architecture is important to think about. But there’s a difference between actually implementing for scale and giving yourself the options to scale when you need… Read More »Scaling Software Architecture Without Overengineering

I’ve noticed a trend, and a lot of people are saying the same thing: just use Postgres as a queue. No Kafka, no Redis, no RabbitMQ, just one database for everything. And I totally get it. I get the appeal. There are fewer moving parts. There is less infrastructure. There is only one thing to run. But what feels simple at the very beginning can often lead to a lot of complexity later. It’s like using Excel when you really need a database. Sure, it holds data. You understand Excel well. But are you really about to build a relational… Read More »Just Use Postgres as a Queue?

I get it. Most apps really are that simple. Typically, just CRUD. A user submits a form, you validate some data, save it in a database somewhere, and return a response. That is it. So is Event-Driven Architecture Overkill then? YouTube Check out my YouTube channel, where I post all kinds of content on Software Architecture & Design, including this video showing everything in this post. Event-Driven Architecture Overkill? This topic stemmed froma Reddit post that I thought was pretty interesting. Primarily because it’s confusing a lot of concepts and seems to miss the point of Event-Driven architecture. So that’s what this… Read More »Is Event-Driven Architecture Overkill for Most Apps?