Fundamentos de la arquitectura serverless

Serverless computing is an execution model where the cloud provider dynamically manages the allocation and provisioning of servers. You, as the developer, don't have to think about servers at all!

Instead, you write and deploy code, and the cloud provider runs it only when needed. This abstracts away the underlying infrastructure, letting you focus purely on your application logic.

The most common form of serverless computing is Function as a Service (FaaS). Here, you deploy individual functions that perform specific tasks.

• Each function is a small, independent piece of code.
• It runs in response to an event.
• It automatically scales from zero to thousands of instances.

Think of it as microservices taken to the extreme: nano-services!

Serverless functions don't just run continuously; they are triggered by events. An event is anything that happens in your system that a function can react to.

Common event sources include:

• HTTP Requests: For API endpoints.
• Database Changes: When data is added or updated.
• File Uploads: To storage like S3 or Blob Storage.
• Queue Messages: From message queues.

This makes them perfect for reactive architectures.

Serverless architecture offers compelling advantages for SaaS:

• Automatic Scaling: Functions scale instantly with demand, no manual intervention.
• Pay-per-Execution: You only pay when your code runs, often saving costs.
• Reduced Operational Overhead: No server patching, maintenance, or infrastructure management.
• Faster Time-to-Market: Developers focus on code, not infrastructure.

These benefits contribute to highly scalable and efficient SaaS components.

Serverless computing is ideal for many SaaS use cases:

• API Backends: Building lightweight, scalable REST APIs.
• Data Processing: Responding to new data uploads (e.g., image resizing, document conversion).
• Scheduled Tasks: Running daily reports or batch jobs without dedicated servers.
• Chatbots & Webhooks: Event-driven interactions with external services.

It's great for handling variable loads efficiently.

While both offer flexibility, serverless and containers (like Docker) have different abstraction levels:

• Containers: You package your application and its dependencies into an isolated unit. You still manage the servers (or a container orchestration platform) that run these containers.
• Serverless: You deploy just your code. The cloud provider handles everything else, including the underlying containers, VMs, and scaling.

Serverless offers a higher level of abstraction and less operational burden.

All major cloud providers offer robust serverless platforms:

• AWS Lambda: The pioneer and widely used.
• Azure Functions: Microsoft's offering, integrated with Azure ecosystem.
• Google Cloud Functions: Google's solution, well-integrated with GCP services.

These platforms provide the runtime environments, event integrations, and scaling capabilities that make serverless possible.

Here's a basic Python example of a serverless function. It takes an input event, processes it, and returns a structured response. Imagine this function being triggered by an HTTP request.

In this lesson, we explored the fundamentals of serverless architecture:

• It abstracts away server management, letting you focus on code.
• FaaS is the core model, where code runs as event-triggered functions.
• Benefits include automatic scaling, pay-per-execution, and reduced ops.
• It's excellent for reactive SaaS components like APIs and data processing.

Serverless offers a powerful way to build scalable and cost-efficient backends.