Fundamental Terminology and Concepts Flashcards

1
Q

Cloud Computing

A

-Cloud computing is a specialized form of distributed computing that introduces utilization models for remotely provisioning scalable and measured IT resources

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

IT Resource

A

-A physical or virtual IT-related artifact(software or hardware). ex: physical server, virtual server, software program, service, storage device, network device

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

Virtualization

A
  • Allows physical IT resources to provide multiple virtual images of themselves so that their underlying processing capabilities can be shared individually by multiple consumers.
  • The owner of the IT resource maintains centralized administrative control and intentionally hides implementation details from consumers of the virtual IT resources
  • This abstraction of the physical IT resource allows consumers to use the provided virtual IT resources without and required knowledge of how the underlying physical IT resource exists or operates.
  • As consumer usage demand fluctuate, the owner of the physical IT resource can scale it accordingly
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Scaling

A

Represents the ability of the IT resource to gracefully handle increased or decreased usage demands

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

Horizontal Scaling

A
  • The allocation or releasing of resources of the same type

- Is a common form of scaling within cloud environments.

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

Vertical Scaling

A
  • Occurs when an existing resource is upgraded or replaced by another
  • Less common in in cloud environments due to potential downtime that may be required to scale up or down
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

(Horizontal) Scaling out

A
  • The horizontal allocation of resources
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

(Horizontal) Scaling in

A
  • The horizontal releasing of resources
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

(Vertical) Up Scaling

A
  • The upgrading of an IT resource or the replacing of an IT resource with that has higher capacity
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

(Vertical) Down Scaling

A
  • The downgrading of an IT resource or the replacing of an IT resource with another that has lower capacity
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Cloud

A
  • A distinct and remote IT environment designed for the purpose of remotely provisioning scalable and measured IT resources.
  • IT resources are provided by a cloud for consumers to access remotely, from outside the cloud perimeter.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

On-Premise

A
  • Used to qualify an IT resource that is not remotely accessible via a cloud, but instead resides with an internal IT enterprise environment.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Service

A
  • From an implementation perspective, a service is a software program that can be remotely invoked via a published technical interface (or API) referred to as a service contract
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Service Consumer

A
  • When a software program invokes and interacts with a service, it is labeled as a service consumer
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Service Composition

A
  • When two or more services participate to complete a given task
  • Services acting as service consumers can invoke other services.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Cloud Service

A
  • Any remotely accessible IT resource
17
Q

Service Agent

A
  • An event-driven program capable of transparently intercepting and processing messages sent to or from services
  • Depending on the development platform you are working with service agents may be called “filters”, “listeners”, “interceptors”, “handlers”, etc.
  • Do not have a technical interface (or service contract) and are therefore not explicitly invoked
  • Common functions are routing, logging, validation and security-related processing.