Amazon Web Services
Compute
- AWS EC2
- EC2 Instance Types
- EC2 Pricing Models
- EC2 Auto Scaling
- Elastic Load Balancing-ELB
- AWS Lambda – Serverless Computing
- Amazon Lightsail
- AWS Elastic Beanstalk
- AWS Fargate
- Amazon ECS (Elastic Container Service)
- Amazon EKS (Elastic Kubernetes Service)
Storage
- S3 vs. EBS vs. EFS
- Amazon S3 (Simple Storage Service)
- Amazon S3 Storage Classes
- Amazon EBS (Elastic Block Store)
- Amazon EFS (Elastic File System)
- AWS Storage Gateway
- AWS Snowball
- Amazon FSx
- AWS Backup
Database Services
- Amazon RDS
- Amazon Aurora
- Amazon DynamoDB
- Amazon ElastiCache
- Amazon Redshift
- AWS Database Migration Service (DMS)
- Amazon Neptune
- Amazon DocumentD
Networking and Content Delivery
- Amazon VPC
- Subnets
- Internet Gateway
- AWS Direct Connect
- AWS Route 53
- AWS CloudFront
- AWS Transit Gateway
- Elastic IP Addresses
DynamoDB
- DynamoDB Global Table vs Regular DynamoDB Table
- DynamoDB Streams
- Athena query data to DynamoDB
- Athena Query Results with DynamoDB
- PySpark DataFrame to DynamoDB
Redshift
Lambda
Glue
Lambda
Security
DynamoDB Global Table vs Regular DynamoDB Table
A DynamoDB Global Table is a multi-region, fully replicated version of a standard DynamoDB table, allowing for real-time data synchronization across multiple AWS regions. In contrast, a regular DynamoDB table is region-specific and only exists in a single AWS region.
2. Key Differences
Feature | Regular DynamoDB Table | DynamoDB Global Table |
---|---|---|
Replication | No automatic replication | Multi-region replication |
Availability | Limited to one region | Available in multiple regions |
Latency | Single-region access | Lower latency for global users |
Write Conflicts | No conflicts | Uses last writer wins conflict resolution |
Use Case | Local applications, single-region workloads | Multi-region applications, disaster recovery |
3. Scenario
📌 Scenario: Multi-Region E-Commerce Application
Imagine an e-commerce company with customers in North America and Europe. If the DynamoDB table is in us-east-1 (Virginia) but a customer in eu-west-1 (Ireland) accesses it, they will experience high latency due to cross-region requests.
✅ Solution: DynamoDB Global Table
- A Global Table is created in us-east-1 and eu-west-1.
- Customer data is automatically synchronized between both regions.
- A user in Europe gets fast responses from the DynamoDB instance in eu-west-1 instead of querying us-east-1.
4. Architecture Diagram
🔹 Regular DynamoDB Table
+-----------------+| DynamoDB (us-east-1) |+-----------------+ | | (High latency for global users) vCustomers in EU and Asia experience delay
🔹 DynamoDB Global Table
+-----------------+ +-----------------+| DynamoDB (us-east-1) | <--> | DynamoDB (eu-west-1) |+-----------------+ +-----------------+ | | v vUsers in US Users in EU get low latency
- Data is replicated automatically.
- Write conflicts are handled with last-writer-wins.
5. When to Use DynamoDB Global Tables?
✅ Multi-region applications (e.g., global SaaS products)
✅ Disaster recovery and failover (e.g., ensuring data availability if one region fails)
✅ Low-latency access for worldwide users
Would you like help setting up a Global Table in AWS? 🚀