[eric4smith]

Every project should be started as a monolith. Period.

Then as it grows and it makes sense to decouple at the edges then it makes sense.

And these micro services only make sense when there is a team responsible for each one.

Otherwise the whole thing is like a game of chess - you will forget to make a move at some point.

[bwship]

This seems to be a little over-simplistic. There are many good cases for microservices, and there are times when going into the project, you know it is what is needed. I think there are also a number of ways to make microservices, and it doesn't have to always be difficult. For instance, the last 4 projects I have built have been done with microsoervices, where the API Gateway endpoints such as /user or /machines each talk to their own lambda microservice.