[sleiben]

We use the microservices architecture as a single team and don’t have any issues with this for many years. The key is to have a monorepo and stay consistent by following strict coding guidelines.

In my opinion it makes the backend way more resilient than a monolith.

Don’t kill me for this opinion please ;)

[BoorishBears]

How does it make the backend more resilient than a monolith? Do you not realize you have multiple instances of a monolith or something?

[jabradoodle]

There are some reasons it may lead to resiliency; another teams features slow dB queries not being on your db, teams not mutating data in a shared db, memory leaks in someone elses feature not taking your app down. Being able to choose language/libraries and tune the runtime to your requirements.

Of course when you replace function calls with network calls, make everything asynchronous and eventually consistent, there is a lot of work to do to not end up with a less reliable system.

[ahoka]

Bad input crashes app, monolith fails over, other instance crashes. Full outage. Assuming proper vertical separation, this risk can be reduced by microservices.