Global infrastructur Flashcards
1
Q
Why make a global application?
A
- deployed in multiple geographies
- Decreased Latency, Disaster Recovery, Attack protection
2
Q
Global Applications in AWS
A
- Global DNS: Route 53, Global CDN: CloudFront, S3 Transfer Acceleration, AWS Global Accelerator
3
Q
Amazon Route 53
A
- Managed DNS
4
Q
Route 53 Routing Policies
A
- SIMPLE ROUTING POLICY (no health check)
- WEIGHTED ROUTING POLICY (Routing 70% to one EC2-Instance, less to other)
- LATENCY ROUTING POLICY (näherste Resource)
- FAILOVER ROUTING POLICY (Disaster Recovery)
5
Q
Amazon CloudFront
A
- Content Delivery Network (CDN)
- Improves read performance, content is cached at the edge
- DDoS protection, Shield, WAF
6
Q
CloudFront vs S3 Cross Region Replication
A
- CloudFront: Global Edge network
- S3 Cross Region Replication: Must be setup for each region
7
Q
S3 Transfer Acceleration
A
- Increase transfer speed by transferring file to AWS edge location
8
Q
AWS Global Accelerator
A
- Improve global application availability and performance using the AWS global network
9
Q
AWS Global Accelerator vs CloudFront
A
- both use the AWS global network and its edge locations
- CloudFront: Improves performance for cache
- Global Accelerator: no caching, proxying packets at the edge
10
Q
AWS Outposts
A
- “server racks” that offers the same AWS infrastructure, services, APIs & tools for on-premises
- AWS will setup and manage “Outpost Racks”
11
Q
AWS WaveLength
A
- Brings AWS services to the edge of the 5G networks
- Ultra-low latency applications
12
Q
AWS Local Zones
A
- Bring AWS resources (compute, database, storage, …) closer to your users
- Good for latency-sensitive applications
13
Q
Global Applications Architecture
A
- Single Region, Single AZ (low availibility and latency, easy to set up)
- Single Region, Multi AZ (high availibilty, low latency, medium to set up)
- Multi Region, Active-Passive (high global reads, low global writes medium to set up)
- Multi Region, Active-Active (high reads and writes, hard to set up)
