L6a - Cloud as Service Flashcards

1
Q

On-premise to cloud. List all approaches in order.

A
  1. Traditional on-premise
  2. Colocation
  3. Hosting
  4. Infrastructure as service
  5. Platform as service
  6. Software as service
  7. Serverless
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

What is Iaas?

A

renting a computer

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

What are the different options for IaaS?

A
  1. renting a VM (actual node is shared)
  2. dedicated server (virtualised but not shared)
  3. bare metal
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Who is IaaS good for?

A

useful to those who need access to computers but can/want to build the rest of the stack themselves

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

List 4 drawbacks of virtualisation (shared setting) ?

A
  1. Performance overheads
  2. Performance isolation
  3. Shared environments complicate licensing
  4. Shared environment may create legal issues
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Explain PaaS.

A

You are only responsible for the data and the application.

You get the computers and the middleware, you build
the application.

In Platform as a Service, what is “rented” is not just an instance but the whole software and hardware infrastructure needed to run an application. (including OS).

The user still puts the application together using the services provided but PaaS reduces the amount of code to produce and takes advantage of the cloud features.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Why does PaaS make sense? / Why is it possible?

A

Some apps use the same subset of features.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Explain SaaS.

A

You get the application provided by the cloud, you provide the data to populate it.

e.g. Microsoft Office 365, gmail, Dropbox
e.g. Snowflake for enterprises (data analytics)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Explain FaaS.

A

FaaS (Function as a Service) allows to encapsulate a small application into a function (e.g., a container image) and then the cloud takes over all tasks related to executing it.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

List 4 properties of FaaS.

A
  1. no reservation of VM or provisioning of instances
  2. automatic scalability
  3. automatic triggering
  4. charged by the millisecond
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

What are the advantages of FaaS?

A
  1. for very short tasks executed rarely, much cheaper (not true for longer tasks, serverless more expensive per hour than VM instances)
  2. functions can be started very quickly and automatically (VM instances can take a long time to start and be ready to process data)
  3. elasticity is automatic (if more functions are needed, the cloud just spawns more)
  4. no need to set up complicated system
  5. automatically coupled to events
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

What are the drawbacks of FaaS?

A
  1. stateless
  2. short lived
  3. no communication across functions

extra: data processing is not good for serverless

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

What is the reasoning behind serverless?

A

remove the need to deploy a complex infrastructure for every job, automate deployment and execution

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

What does serverless run on?

A

small footprint VMs/containers

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

How does serverless work, step by step.

A
  1. User provides code for a “function” and selects a size (typically in amount of memory, which maps to a number of virtual CPUs)
  2. The function is registered in the system (an image created and stored)
  3. The user invokes a function, or it is triggered by an event
  4. The serverless platform allocates a micro-VM, loads the image, and starts the function
  5. The platform takes care of scaling it up (call more instances of the function) and tear it down when done
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

What are the challenges of serverless for the provider?

A
  1. functions need to stay warm to ensure short start up time (need to reserve containers etc.)
  2. scheduling is hard at this level of granularity