[bitcurious]

I'll go against the grain and say that microservices have advantages for small dev teams embedded in non-tech orgs.

1. You get to minimize devops/security/admin work. Really a consequences of using serverless tooling, but you land on a something like a microservices architecture if you do.

2. You get can break out work temporally. This is the big one - when you're a small team supporting multiple products, you often don't have continuity of work. You have one project for a few months, completely unrelated product for another few months. Microservice architectures are easier to build and maintain in that environment.

[roguecoder]

Watch out for bit rot, though: it is very easy for a startup to come back to one of those microservices six months later and discover the dependencies are borked and it no longer even builds.

Each repo you create is one more set of Dependabot alerts you need to keep on top of.

[bilbo-b-baggins]

That’s just a devops failure tho. Nothing to do with microservices. And Renovatebot can batch updates weekly in single PRs if the toil is bad, which really cuts down and makes the load easy to bear.

[codr7]

Microservices minimize devops/security/admin work?

What planet are you living on?

[roguecoder]

I assume he means building the product out of AWS legos like Lambdas. Stick it all under one account, manage it manually instead of trying to deal with Terraform and it isn't too bad.

Heroku is still way easier, though.

[mdaniel]

> manage it manually instead of trying to deal with Terraform and it isn't too bad

I'm firmly in team "fuck Terraform" but I'm also in team "read only console access" because otherwise "how did this thing get this way" is insanity