Web Services 1

Question 1

• 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

Answer 1

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.

Question 2

What triggers code execution?

Answer 2

• 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

Question 3

Why is Serverless attractive?

Answer 3

• 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.

Question 4

key factors for infrastructure cost savings

Answer 4

• high availability
• multi-region deployment
• cover delta between short load spikes and valleys
• example incremental cost

Question 5

example serverless

Answer 5

• chatbot
• Nordstrom Recommendations

Question 6

What is Serverless good for?

Answer 6

• short-running
• stateless
• event-driven

1. microservices
2. mobile backends
3. bots, ML inferencing
4. IoT
5. Modest Stream Processing
6. Service Integration

Question 7

Serverless is not good for

Answer 7

• long running
• stateful
• number crunching

1. deep learning training
2. databases
3. heavy-duty stream analytics
4. numerical simulation
5. video streaming

Question 8

Current Platforms for Serverless

Answer 8

1. AWS Lambada
2. Open Lambada
3. Fission
4. Google Function
5. Red-Hat
6. IBM Cloud Functions
7. Iron.io
8. OpenWhisk
9. fn
10. Azure Function