To be fair, you CAN build a monolith in a way that is very similar to microservice architecture. You can have a single function that handles all data base writ

To be fair, you CAN build a monolith in a way that is very similar to microservice architecture. You can have a single function that handles all data base writes. A single function that monitors for failures. A single function that sends outbound notifications... etc If these functions are call in a way that: allows for A/B testing, SUPER high latency (or no response), failure notifications sent to the code owner, automatic retries of failures, independent code deploys Then, congratulations, you have a monolith made up of microservices!