Elasticity and Scalability Flashcards

1
Q

Scalability

A

focus on building for growth;

keep storing more and more data without having to provision any hardware.

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

Elasticity

A

ability to scale up and scale down
pay only for what you need, when you need it.
– increase or decrease read and write throughput capacity on demand.

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

EC2 – Scaling and Elasticity

A
Scalability:
 -- Increase the size of instances
-- choose different instance types
-- launch more instances
Elasticity:
-- auto scaling gives the ability to grow and shrink back .
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Amazon RDS and ElastiCache

A
    • Reserved capacity is available
    • New generation of Reserved Cache Nodes only offer Heavy Utilization nodes, while older generations offer Heavy, Medium, and Light Utilization
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

AutoScaling vs. Resizing

A

auto scaling: distributes the load across multiple instances; uses metrics and rules to automate spinning up/terminating instances; can scale or shrink on a schedule.
Resizing instances: Increases/decreases resources available to our application

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

Challenges of Auto Scaling

A

relatively complicated to setup
– instances can be started and stopped at any time;
– Applications need to be designed to handle distributed work
– important data needs to stored in a central location
–if one server terminates, the application should still function;
Delays in scaling
– Instances take time to initialize
– applications may require setup which could take even more time.

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

Challenges of Resizing Instances

A

Compatibility
– instances must have the same virtualization type to resize;
– incompatible instances require migration
EBS-backed instances need to be stopped before resizing
instance store-backed instances require migration by creating an image and launching a new instance from that image.
Resizing is not very flexible compared to auto scaling
usually has to be downtime and careful planning
resizing instances in auto scaling groups may need “suspending”

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