Refactoring to Serverless: From Application to Automation | Amazon Web Services
Briefly

Serverless technologies not only minimize the time that builders spend managing infrastructure, they also help builders reduce the amount of application code they need to write. Replacing application code with fully managed cloud services improves both the operational characteristics and the maintainability of your applications thanks to a cleaner separation between business logic and application topology.
Since the launch of AWS Lambda in 2014, serverless has evolved to be more than just a cloud runtime. The ability to easily deploy and scale individual functions, coupled with per-millisecond billing, has led to the evolution of modern application architectures from monoliths towards loosely-coupled applications.
Modern distributed architectures with independent runtime elements have a distinct topology graph that represents which elements talk to others. The topology has a major influence on the application's runtime characteristics like latency, throughput, or resilience.
Cloud automation languages, commonly referred to as IaC (Infrastructure as Code), date back to 2011 with the launch of CloudFormation, which allowed users to declare a set of cloud resources in configuration files instead of issuing a series of API calls or CLI commands. Initial document-oriented automation languages were soon complemented by frameworks like AWS Cloud Development Kit (CDK), CDK for Terraform, and Pulumi.
Read at Amazon Web Services
[
|
]