On: You want microservices, but do you need them?

[dzonga]

microservices were an effect of the ZIRP era. you literally have places like Monzo bragging that they've 3 microservices for each engineer.

3 tier architecture proves time and time again to be robust for most workloads.

[LaurensBER → dzonga]

1 micro-service per pizza sized team seems to work pretty well.

Put it into a monorepo so the other teams have visibility in what is going on and can create PRs if needed.

[LtWorf → LaurensBER]

Uh? You eat less than a pizza per person?

[SiempreViernes → LtWorf]

To be fair pizzas are quite easy to scale from small kid sizes up to enough for several persons.

But it is a bit sad that the poster apparently never bought a pizza just for themselves.

[LaurensBER → LtWorf]

It's a reference to Amazon's statement that teams should never grow larger than a team that you can feed with 2 (large) pizza's.

The optimum is probably closer to 1 than to 2.

[hackpelican → LtWorf]

8x engineer

[Uvix → dzonga]

Certainly no more than three tiers.

"Traditional" three-tier, where you have a web server talking to an application server talking to a database server, seems like overkill; I'd get rid of the separate application tier.

If your tiers are browser, web API server, database: then three tiers still makes sense.