On: Ask HN: Why Not Microservices?

[tuyguntn]

* more than 10 teams? -> microservices. this brings adding some guidelines: strict communication guidelines (api, events, cross team meetings)

* compliance requirements? -> (micro)services. you need to host some data and workers in separate guarded environments

* too many legacy third party dependencies which might fail or stop whole processes? -> wrap with service

* different independent products in a company? services

for everything else use monoliths

[cweill → tuyguntn]

+1 I think this is the most comprehensive answer. Default to using monoliths whenever possible. More Simple = more robust, more complex = more fragile.