This document discusses serverless computing and its benefits. Serverless allows developers to build and run applications without managing infrastructure. It scales instantly to handle changes in load, and developers do not need to worry about server maintenance, upgrades, or other operational tasks. Serverless computing uses functions as a service and is supported by major cloud providers like AWS Lambda, Azure Functions, and Google Cloud Functions. It is well suited for use cases like microservices, background tasks, image processing, and APIs. While serverless improves deployment speed and scalability, it also has limitations around visibility and timeouts.

1. Serverless
Increasing Software Delivery

2. Contents
- What is Serverless
- Serverless Providers
- Use Cases
- Pros and Cons
- Anatomy of an AWS Serverless Application
- Serverless Architecture
- Demo
- Conclusion

3. What is Serverless ?
It is a technology that helps Developers to deliver
software faster and better and saves Operations
of worrying about server maintenance, upgrade,
security fixes, optimization and other operations
task.
It runs a function as a service and scales almost
instantly to handle load

4. What is Serverless ?
Serverless technology is language-based. Some of the languages
supported currently include:
- NodeJS
- Python
- C#
- Java
- Golang

5. Serverless
Serverless technology is provided at scale by the major cloud
providers. But there are open-source tools that you can use to have
a self-hosted serverless system.
- AWS: Lambda
- Azure: Azure Functions
- GCP: Google Functions
- IBM: OpenWhisk

6. Use Cases
- Microservices
- Background API calls
- Bots
- Image Compression
- File Upload
- And more ...
NB: Serverless generally cannot be used for any operation that
holds a connection open. E.g. RabbitMQ Consumer

7. Pros and Cons
Pros
- Fast and Easy to Deploy (when using a Framework)
- No need to worry about server resources
- No need to worry about server maintenance and updates
- Improves release frequency and lead time for changes
- Helps to scale from thousands to millions of calls without any
form of intervention
- Provides a homogenous architecture for the full Software
Development Life Cycle

8. Pros and Cons
Cons
- Does not apply to all use cases of software delivery
- No access to the underlying infrastructure
- There is no visible system metrics
- Has a timeout to run a function

9. Anatomy of an AWS Serverless
Application
- API Gateway (Optional)
- Lambda Function
- Code
- Function Handler
- Function Name

10. Serverless Architecture

11. Serverless Architecture

12. Serverless Architecture

13. Demo
- Python: AWS Chalice (https://chalice.readthedocs.io/)
- NodeJS: Serverless (www.serverless.com)

14. Conclusion
Serverless is not the silver bullet to building APIs but it holds great
promise in the world of APIs as from the advantages that I have
stated
Adoption of this will help us to improve delivery and drive down
cost drastically
Thank you

15. Thank you