Serverless
With managed serverless services, the provider operates the execution infrastructure. Code, access and error handling remain application responsibilities.
What does serverless mean?
Serverless describes a model in which a platform provides and manages the required execution infrastructure. The application team does not need to operate its own server instances for this. AWS lists functions, container execution and other services under serverless. Function as a Service is therefore one form of it; the term extends beyond an individual function.
Servers still exist. In a managed offering, the provider operates them. If an organisation operates the serverless platform itself, its infrastructure remains that organisation’s responsibility. Scaling, billing and limits must be clarified for the particular service.
Example: running a report in a container
In the fictional design, a managed service runs the reporting container for job JOB-77. Input data and the result reside in explicitly connected storage services. The team decides who may start the job, which data the container can read and how an error becomes visible. These connections are part of the design, not automatically promised platform features.
OWASP still assigns application code, dependencies, identities and configuration to the team using the service. In the example, it must also decide how to retry the same job safely. Serverless describes the division of operational work here; it proves neither that a correct report was produced nor that total costs are always lower.
Sources
Related terms
- FaaSFunction as a Service runs deployed functions in response to events or calls. A platform provides and manages the execution environment.
- PaaSPlatform as a Service provides a platform for custom applications. The team deploys its code; the provider operates the underlying environment.
- ContainerA container runs application processes in an isolated environment. It can simplify deployment, while backups and operational responsibilities remain necessary.
- Return-PathReturn-Path records the SMTP reverse path in a header. It explains the technical route for error reports, not a person’s identity.
- Envelope-FromEnvelope-From identifies the SMTP sender for transport and error feedback. It must be distinguished from the visible sender address.
- DMARC aggregate reportA DMARC aggregate report summarises a reporting mail system’s domain checks over a period. It helps examine sending sources and misconfigurations.
Articles on this topic
Cloud & Operations with ASES
Hosting, deployment, maintenance and support