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.
3 tier architecture proves time and time again to be robust for most workloads.
Put it into a monorepo so the other teams have visibility in what is going on and can create PRs if needed.
But it is a bit sad that the poster apparently never bought a pizza just for themselves.
The optimum is probably closer to 1 than to 2.
"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.