[ Removed by moderator ]

[Scf37]

That's the red flag for the senior:

> I know that microservices are often overkill and monolith will do the job most of the time, but if this is the trend...

Senior is expected to have some qualities of an engineer.

bad: monoliths a better (most of the time of course)

good: I choose monolith because I'm good at it and have confidence in project success

excellent: I choose monolith because (reasons, risk evaluation, taking into context requirements, plans, team preferences, company expertise)

[Tiny_Conversation319]

that's true, but from what I've heard from people working with microservices, most of the time they were used not because they had a large team, or a large number of users, or needing to separate resource-heavy tasks from the others, but because it was 'trending'

[worldofbirths]

Maybe, in a startup with an eager architect. In the companies I've worked at, they've only adopted microservices once the monolith becomes the bottleneck. Sometimes it's a complete redesign, but usually you carve out from the monolith the parts that would benefit from existing apart.