Upload
others
View
8
Download
0
Embed Size (px)
Citation preview
Functional Programming in Serverless World
Big Data Moscow 2018 (11.10.2018)
~ # whoami (afronski)
✓ Co-founder and Functional Aficionadoat Pattern Match
Erlang, Elixir, Node.jsAWS (3 certificates)
✓ Co-organizer of Functional Miners
What is serverless?
There are servers
There are ops
read.acloud.guru/iaas-paas-serverless-the-next-big-deal-in-cloud-computing
Serverless
Back-end as a Service (BaaS)
Function as a Service (FaaS)
Incoming Event
Source Code Package Configuration
Function (Execution Unit)
RAM: 512 MB
RAM: 512 MB 0.5 GB
Real time: 120 msBill time: 200 ms (buckets by 100 ms)
Price: 0.00001667 GB * seconds
Cost: 0.00001667 * 0.5 GB * 0.2 s = 0.000001667 USD = 1.7 μUSD
Response
Whyserverless?
www.doc.ic.ac.uk/~rbc/papers/fse-serverless-17.pdf
Gojko Adzic - Designing for the Serverless Age (GOTO 2017)
Costs
Architecture[...] breaking the monolith into functions that could be independently deployed, meant that they were better able to split the team up to work on more things in parallel, and to deploy each feature separately.
Operations[…] so their estimate is that moving to Lambda gave an operational cost reduction of greater than 95% for a comparable amount of compute.
Technology
Shims
Using Node.js process API to spawn an
executable
Handling events reported by subprocess and passing results to
the AWS Lambda handler
Sending input arguments to the
spawned subprocess
Measurements
Test Scenarios1. Two endpoints:
a. Echoing incoming body.
b. Sieve of Eranthoses (naive implementation).
2. Package Size.
3. Memory Usage (dependent on input argument).
4. Execution Time (dependent on input argument).
5. Startup Time (cold start, no work done).
"Situated" Programs (from Rich Hickey's keynote at Clojure/Conj 2017)
How long does AWS Lambda keep your idle functions around before a cold start? Serverless: Cold Start War
Constraints
Constraints1. No knowledge about container and its reuse.
2. New approach requires new paths.
3. Limits everywhere!
4. Provider limitations.
5. VM optimizations required from the get go.
6. Beware the toolchain!
Summary
Safe default:F# on Azure or AWS
(.NET Core 2.0)
Tooling is King
Context is King
Thank you!Questions?
References
1. Our company - Pattern Match and my talks.2. Functional Miners meet-up (facebook, twitter, github, email, website).3. Serverless Architecture, Serverless (Martin Fowler’s articles).4. AWS Lambda, Google Cloud Functions, Azure Functions.5. Container Reuse in AWS Lambda, Serverless: Cold Start War.6. Running Executables in AWS Lambda.7. Serverless Computing: Economic and Architectural Impact.8. Why the JVM is a Good Choice for Serverless Computing.9. Droplr Serverless Revolution.
10. Optimizing Enterprise Economics with Serverless.11. Should I use AWS Lambda or EC2?12. AWS Lambda support for .NET Core 2.0.13. Repository with examples, scripts, and measurements.