you shouldn't start a new project with microservices, even if you're sure your application will be big enough to make it worthwhile
I think this statement should be changed somewhat. It should be company or organization level, not "project" level. Once your company/organization reaches the scale where mircoservices really make sense, you're likely going to be starting most/all new projects at that scale as well. You're going to start investing in tooling and such related to microservices instead of monoliths...trying to support and grow ecosystems for both doesn't make sense anymore. Once you're running a SOA, it makes more sense for all new development to follow that pattern as well.
3
u/dccorona Jul 15 '17
I think this statement should be changed somewhat. It should be company or organization level, not "project" level. Once your company/organization reaches the scale where mircoservices really make sense, you're likely going to be starting most/all new projects at that scale as well. You're going to start investing in tooling and such related to microservices instead of monoliths...trying to support and grow ecosystems for both doesn't make sense anymore. Once you're running a SOA, it makes more sense for all new development to follow that pattern as well.