Serverless
Camilo Hernández
What is this about?
- What is serverless?
- Personal experience
- Development process
- Advantages and Disadvantages
- When and When not
What is serverless?
- Serverless is an architectural trend that tries to “reduce all notion of infrastructure”
- A paas with pay per use.
- Ephemeral compute ( There is not constantly running server).
- There is also no runtime permanently listening on an IP address and open port.
- You pay only for the invocation of the function
- The scaling is automated
- there is no configuration for the number of function instances required
What is serverless?
Google Beta
Personal Experience
- Crawlers
- Async Set up
- Image Processing
- Batch for ML
- ETL from legacy systems
Benefits
-
“never pay for idle” concept is attractive
-
Easy onboard
-
Easy deploy
-
Reduce dev ops investment
-
Adds some developer independence
-
Architectures are inherently scalable
Disadvantages
-
Vendor lock-in
-
The function itself is triggered by a typed, cloud-provider-specific event.
-
Testing and debugging become more challenging
-
new security concerns
-
built for long-running processes
-
Performance may be affected
When
-
You see an opportunity to reduce costs
-
You want to have some "hardware independence"
-
You don't want to worry about scale up and down manually
-
You want to monitor in a easy way your services
-
Cron tasks with small processing.
-
Event triggering (ex: msg)
-
inconsistent traffic
When not
-
You can't live with cold starts
-
You want flexibility to move easily out of the cloud provider
-
You are not willing to automate
-
specific security concerns
-
specific gateway or networking integrations.
-
built for long-running processes
-
You need to develop something fast and it's your first time with lambdas
-
large applications with a fairly constant, predictable workload