Having run a project with a very small team and microservices, from scratch, for ten years: nope. Unless you are going to invest heavily in training and education for your devs, unless they are used to distributed architecture: nope.
I get your cto's points. It's why I made the choice to go microservices in the first place. However, unless you have an excellent ops team, an excellent toolsmith or six, I highly suggest not to do it. If you have a very very small amount of services, maybe, but by definition the amount of them grow. You need so many tools and such a buttoned up ci/cd process. Deployments and rollbacks need to be very automated. Qa needs to be very automated. You need to automate ALL the things with that few people.
We started with about 8 services. We are now up to around 35. It's a LOT to manage with very few heads.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Having run a project with a very small team and microservices, from scratch, for ten years: nope. Unless you are going to invest heavily in training and education for your devs, unless they are used to distributed architecture: nope.
I get your cto's points. It's why I made the choice to go microservices in the first place. However, unless you have an excellent ops team, an excellent toolsmith or six, I highly suggest not to do it. If you have a very very small amount of services, maybe, but by definition the amount of them grow. You need so many tools and such a buttoned up ci/cd process. Deployments and rollbacks need to be very automated. Qa needs to be very automated. You need to automate ALL the things with that few people.
We started with about 8 services. We are now up to around 35. It's a LOT to manage with very few heads.