CodeOpinion

You have a multi-tenant system, but you discover a pretty horrible bug.

Have you ever changed your backing data model and then all of a sudden all your clients explode?

You finally did it.

So, you broke apart your monolith.

What happens when someone clicks the Place Order button?

You can follow every enterprise best practice.

You start off with what seems like the obvious solution to a multi-tenant SaaS application.

You wanted your system to be resilient, so you followed the standard advice.

So, you adopted event-driven architecture because your system was a rat’s nest of coupling, and events were the answer to decouple it.

You start with a simple entity.

So you built a modular monolith.

Modular monoliths are all the rage.

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.

So, you built an elaborate system with commands, queues, an event-driven architecture, retries, timeouts, and, most importantly, compensating actions all handled within sagas.

A post on Medium was shared with me by a member of my channel.

I’ve noticed a trend, and a lot of people are saying the same thing: just use Postgres as a queue.

In my last video, I said that clean architecture was killing your velocity.

We’ve been told that clean code and deadlines are opposites.

I get it.

I keep seeing posts pushing back on the idea that coding isn’t the hard part.

How do you share code between vertical slices?

What’s overengineering?