Web Services 1 Flashcards
- a cloud-native platform for
- short-running, stateless computation and
- event-driven applications which
- scales up and down instantly and automaticallyand
- charges for actual usage at a millisecond granularity
Serverless
short tasks that don’t need a server to be running all the time, like handling individual requests from a website or reacting to specific events, like someone uploading a file or sending a message. It’s flexible, cost-effective, and saves you from the hassle of managing servers yourself.
What triggers code execution?
- Runs code in response to events
- Event-programming model
only activated when something specific happens, and it doesn’t just sit idle waiting for things to occur
Why is Serverless attractive?
- Making app development & ops dramatically faster, cheaper, easier
- Drives infrastructure cost savings
focus on building great applications without getting bogged down by the complexities and costs of managing infrastructure.
key factors for infrastructure cost savings
- high availability
- multi-region deployment
- cover delta between short load spikes and valleys
- example incremental cost
example serverless
- chatbot
- Nordstrom Recommendations
What is Serverless good for?
- short-running
- stateless
- event-driven
- microservices
- mobile backends
- bots, ML inferencing
- IoT
- Modest Stream Processing
- Service Integration
Serverless is not good for
- long running
- stateful
- number crunching
- deep learning training
- databases
- heavy-duty stream analytics
- numerical simulation
- video streaming
Current Platforms for Serverless
- AWS Lambada
- Open Lambada
- Fission
- Google Function
- Red-Hat
- IBM Cloud Functions
- Iron.io
- OpenWhisk
- fn
- Azure Function