The Monolith Whenever I hear “monolith”, I think of a massive LAMP project with a single, burning hot MySQL database. (not always the case). The monolith architecture looks something like this in Serverless: I.e. all requests to go to a single Lambda function, app.js. Users and games have nothing to do with one another but the application logic for users and games are in the same Lambda function. Pros We found that the greatest advantage that the monolith had over nanoservices and microservices was speed of deployment. With nanoservices and microservices, you have to deploy multiple copies of dependant node_modules (with Node.js) and any library code that your functions share which can be slow. With the monolith, it’s a single function deployment to all API endpoints so deployment is faster. On the other hand, how common is it to want to deploy all endpoints… Cons This architecture in Serverless, has similar drawbacks to the monolithic architecture in general: Tighter coupling. In t...