>3. Deploys are very difficult, and as you scale to over 10 developers increasingly becomes difficult to push up (it takes one persons bad commit to hold everyone in the organization from deploying).
I feel that is a way too low number. If don't have good enough engineering practices with branching, pull requests/code reviews, unit/integration tests to handle 10 people then microservices will be painful as well.
I would say like 3+ teams at least to really justify it? You can do it earlier but I don't see it as a necessary benefit.
>7. Microservices can be cheaper when you scale, you don't have the GCD of memory/CPU/disk requirements as you do in a monolith.
Yes, but by default they are more expensive until you reach a certain scale and it needs to be a specific type of scaling.
I feel that is a way too low number. If don't have good enough engineering practices with branching, pull requests/code reviews, unit/integration tests to handle 10 people then microservices will be painful as well.
I would say like 3+ teams at least to really justify it? You can do it earlier but I don't see it as a necessary benefit.
>7. Microservices can be cheaper when you scale, you don't have the GCD of memory/CPU/disk requirements as you do in a monolith.
Yes, but by default they are more expensive until you reach a certain scale and it needs to be a specific type of scaling.