The discussion about monolith vs microservices has been going on for years. And every faction has its fair amount of very good points.

Microservices shit

I must admit that in my career I have encountered microservice applications that were as bad as monolithic ones ( and definetely harder to understand, work with and test!) but my approach of choice is definitely leaning towards a Decoupled Architecture!

Components and services can operate independently from one another, are easier to understand with less domain knowledge and global context and are easier to run and test on their own.

Sure there is still the risk that you have gone from building a pile of mud to orchestrating a lot of shit (dunno where i read this quote...) but that's another story.

Anyway. Decoupled Architecture, we were saying, and Event-Driven Architecture!

Event Driven Architecture

Decoupled and Event-Driven Architectures are patterns that are not exclusive to serverless, but imho its with Serverless where they shine the most!

serverless and event driven architecture

Serverless frees you from a lot of administrative tasks that keep you away from implementing your business logic.

serverless means you don't manage the underlying service that runs the capability

no instances to manage

no hardware provisioning

no management of OS or software

no provisioning and patching

automatic scaling and high availability

very cost effective

Let's have a look what Serverless services AWS provides to build Decoupled, Event-Driven Architectures.