AWS SAA-C03: Route 53 Routing Policies and Failover
Amazon Route 53 is often introduced as managed DNS, but architecture decisions begin after the zone exists. The important question is how DNS…
Read articleTHE EDITORIAL ARCHIVE
All articles.
Perspectives on technology, certifications and practical IT skills.
ARTICLESBrowse the collection
AWS SAA-C03: RDS Multi-AZ vs Read Replicas
RDS Multi-AZ and read replicas are often mentioned together because both involve additional database copies, but their primary purposes are different. Multi-AZ is…
Read articleAWS SAA-C03: Public vs Private Subnets
Public and private subnets are among the first concepts people learn in Amazon VPC, yet the labels are frequently misunderstood. A subnet is…
Read articleAWS SAA-C03: NAT Gateway vs NAT Instance in Modern AWS
NAT remains a common part of AWS IPv4 architectures because private workloads often need outbound access to software repositories, partner APIs, or the…
Read articleAWS SAA-C03: Lambda Concurrency and Resilient Serverless Design
AWS Lambda can scale rapidly without server management, but “serverless” does not mean capacity planning disappears. Concurrency, function duration, retry behavior, event-source semantics,…
Read articleAWS SAA-C03: Elastic Load Balancing Across Application Tiers
Elastic Load Balancing sits at the boundary between clients and application capacity, but it is more than a device that spreads requests evenly.…
Read articleAWS SAA-C03: ECS vs EKS vs Lambda for Application Platforms
Choosing between Amazon ECS, Amazon EKS, and AWS Lambda is really a decision about execution model and operational ownership. All three can host…
Read articleAWS SAA-C03: DynamoDB Partition Keys and Capacity Planning
Amazon DynamoDB can scale to extremely large workloads, but that scalability depends on how keys and access patterns are designed. A table with…
Read articleAWS SAA-C03: Designing for AWS Availability Zones
Availability Zones are one of the most important AWS architecture primitives because they let teams separate resources across independent facilities while keeping them…
Read articleAWS SAA-C03: Cost Optimization: Compute and Storage Choices
Cost optimization in AWS is an engineering discipline, not a monthly exercise in finding the largest line item and shrinking it. Compute and…
Read articleAWS SAA-C03: CloudFront Origin Design and Cache Behavior
Amazon CloudFront can look deceptively simple: point a distribution at an origin, choose a cache policy, and let edge locations serve content closer…
Read articleAWS SAA-C03: Auto Scaling Design for Variable Workloads
Amazon EC2 Auto Scaling is often summarized as “add instances when CPU is high,” but production scaling design is more nuanced. The right…
Read articleAWS SAA-C03: Aurora High Availability and Global Databases
Amazon Aurora separates database compute from a distributed storage layer, which changes how architects think about high availability compared with a traditional database…
Read articleAWS SAA-C03: VPC Design for Multi-Tier Applications
A multi-tier VPC design should make the application’s trust boundaries visible in the network rather than placing every component in one flat subnet.…
Read articleAWS SAA-C03: Transit Gateway for Multi-VPC Networks
AWS Transit Gateway is valuable when a cloud network has outgrown a web of VPC peering connections, VPN attachments, and one-off routing exceptions.…
Read article