The first rule of any technology used in a business is that automation applied
to an efficient operation will magnify the efficiency. The second is that
automation applied to an inefficient operation will magnify the inefficiency.
Bill Gates
IMHO microservices can only work well on a single team if they have really solid DevOps skills and tooling already founded within the team. Otherwise, they are going to amplify all the inefficiencies in your team that are part of your value stream. The velocity of a team with immature delivery skills, practices, and tooling after moving to microservices can even be much, much worse than before.
On the flip side, it can create a much faster velocity and a much more stable system as a whole.
I guess my point is start off on the right foot by making sure your team has a DevOps mindset and builds a strong and lean delivery muscle and then refactor toward microservices.
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.
IMHO microservices can only work well on a single team if they have really solid DevOps skills and tooling already founded within the team. Otherwise, they are going to amplify all the inefficiencies in your team that are part of your value stream. The velocity of a team with immature delivery skills, practices, and tooling after moving to microservices can even be much, much worse than before.
On the flip side, it can create a much faster velocity and a much more stable system as a whole.
I guess my point is start off on the right foot by making sure your team has a DevOps mindset and builds a strong and lean delivery muscle and then refactor toward microservices.