Serverless Computing (Initially managed as FaaS) | Overview.

Serverless Computing (Initially managed as FaaS) - Overview.

Scope:

• Intro,
• The concept:  Serverless,
• Architecture,
• Key Characteristics of Serverless,
• Common Serverless Services on AWS,
• When to Use Serverless,
• When NOT to Use Serverless,
• Insights.

Intro:

• Here’s twtech overview of Serverless computing in the context of AWS and modern cloud architecture:
• Serverless Computing was initially managed as FaaS (Function as a Service). 

The concept:  Serverless 

• Serverless is a cloud computing model where twtech focuses only on writing code.
•  The cloud provider handles the infrastructure like:
• Provisioning, 
• Scaling, 
• Maintenance of servers.

NB:

• Despite the name (serverless), twtech should state that the infra is still built on servers.
• However, the servers privisoned are not managed  by twtech.

Architecture

 Key Characteristics of Serverless

Feature	Description
No server management.	twtech doesn’t provision, scale, or manage servers.
Automatic scaling.	twtech Apps scale up/down based on demand automatically.
Pay-per-use.	twtech only pay for the compute time or executions used.
Event-driven.	Functions or services are triggered by events (e.g., HTTP requests, file uploads, database changes).
Quick deployment.	Faster time-to-market and simplified development workflows.

 Common Serverless Services on AWS:

Service	Purpose
AWS Lambda.	Run backend code/functions without managing servers.
Amazon API Gateway.	Create REST or WebSocket APIs to trigger Lambda or other services.
AWS Fargate.	Run containers without managing EC2 instances.
AWS App Runner.	Deploy web apps and APIs from containers or source code — fully managed.
Amazon DynamoDB.	Serverless NoSQL database — auto-scales and manages throughput.
Amazon S3.	Serverless storage for static files, websites, backups, etc.
AWS Congnito.	It allows developers to add user sign-up, sign-in, and access control to their applications, supporting millions of users.
AWS Kinesis Data Firehose.	Facilitates the delivery of real-time streaming data to various destinations.
Aurora Severless.	It automatically starts up, shuts down, and scales capacity up or down.
Step Function.	To create and manage serverless applications, automating tasks that might involve multiple services and steps.
Amazon EventBridge / SNS / SQS.	Event buses, notifications, and queues for building event-driven apps.

When to Use Serverless:

twtech wants to reduce operational overhead,
twtech app has variable or unpredictable traffic,
twtech is building microservices, APIs, or event-driven apps,
twtech needs to rapidly develop and iterate.

 When NOT to Use Serverless:

• twtech needs fine-grained control over twtech infrastructure.
• twtech runs long-running or stateful processes.
• twtech requires specific OS/kernel-level access.
• twtech workloads are constant and predictable,

twtech insight:

• Serverless computing is about maximizing focus on twtech code and minimizing infrastructure concerns.
• Serverless computing is ideal for: 
• Scalable, 
• Cost-efficient, 
• Agile application development.