Cloud Architecture Terms Flashcards
A look into Cloud Architect
Solutions Architect
A role in a technical organization that architects a technical solution using multiple systems via researching, documentation, experimentation.
Solutions Architect needs to answer these questions
- How secure is this solution? (Security)
- How much is this going to cost? (Cost)
Cloud Architect
A solutions architect that is focused solely on architecting technical solutions using Cloud services.
A Cloud Architect needs to understand the following
Availability, Scalability, Elasticity, Fault Tolerance, Disaster Recovery
High Availability
Your ability for your service to remain available by ensuring there is no single point of failure (have backups or a plan) and/or ensure a certain level of performance (quality).
Elastic Load Balancer
Allows you to evenly distribute traffic to multiple servers in one or more datacenters. If a datacenter or server becomes unavailable (unhealthy) the load balancer will route the traffic to only available datacenters within servers. Based on the demand of traffic.
High Scalability
Ability to increase your capacity based on the increasing demand of traffic, memory, and computing power. Vertical Scale: Scale Up to upgrade to a bigger server. Horizontal Scale: Scale Out which adds more servers of the same size.
High Elasticity
The ability to automatically increase/decrease your capacity based on the current demand of traffic, memory, and computing power.
Horizontal Scaling
Scaling Out: Add more of the same size servers
Scaling In: Remove the underutilized same size servers
Vertical Scaling
Scaling Up: to upgrade to a bigger server.
Scaling Down: generally hard for traditional architecture so you will see more of horizontal scaling.
ASG - Auto Scaling Groups
An AWS feature that will automatically add/remove servers based on the scaling rules set by you.
High Fault Tolerance
The ability to ensure there is no single point of failure. Preventing the chance of failure.
Fail-Overs
Is when you have a plan to shift traffic to a redundant system in case the primary system fails. So the traffic would go to the secondary/backup system.
RDS Multi-AZ
When you run a duplicate standby database in another AZ in case your primary database fails.
Highly Durable
Ability to recover from a disaster and prevent the loss of data.
Disaster Recovery
Solutions that help recover from a disaster.
Cloud Endure DR:
Continuously replicates your machine into a low-cost staging area in your target AWS account and preferred Region enabling fast and reliable recovery in case of IT data center failures.
BCP - Business Continuity Plan
A document that outlines how a business will continue operating during an unplanned disruption in services.
RPO - Recovery Point Objective
The max acceptable amount of data loss after an unplanned data-loss incident, expressed as an amount of time. How much data are you willing to lose?
RTO - Recovery Time Objective
The max acceptable amount of downtime you business can tolerate without incurring a significant financial loss. How much time are you willing to go down?
Disaster Recovery Options
It is based on Cost vs Time.
- Backup & Restore
- Pilot Light
- Warm Standing
- Multi-Site Active/Active
Backup & Restore
You backup data and restore to a new infrastructure.
- lower priority
- cost effective $
- restore data after event
- deploy resources after event
- RPO/RTO Hours
Pilot Light
Your data is replicated to another region with minimal services running.
- less stringent RPO/RTO
- core services
- start & scale resources after event
- more costly $$
- RPO/RTO 10 minutes
Warm Standing
Scaled down copy of your infrastructure running ready to scale up
- business critical services
- scale resources after event
- even more costly $$$
- RPO/RTO minutes
Multi-Site Active/ Active
Scaled up copy of your infrastructure architecture in another region.
- zero down time
- near zero loss
- mission critical services
- highhh cost $$$$
- RPO/RTO real time
