Foundations13 lessons · about 5 hoursVery High complexity

Solution Architecture

How to design a system that meets its requirements, and how to defend every trade-off it makes. Twelve lessons go from a written brief to a reviewed design: the numbers behind availability and scale, load balancers, caches, databases, queues, serverless, failure, recovery, security and cost. Each idea is taught without a provider, then named on AWS, Azure and Google Cloud, to the depth of the AWS Solutions Architect Associate exam. A worked case at the end puts the whole course to work on one realistic problem.

After this course you can

  • Turn a brief into numbers (requests per second, storage, latency and availability targets) and design to them.
  • Choose and combine load balancers, caches, databases, queues, functions and containers, and say what each choice costs.
  • Design for failure and disaster, secure the network and the data, and review a design against the six Well-Architected pillars.

Lessons

13 lessons
1 Requirements and estimatesFunctional and non-functional requirements, constraints, back-of-envelope estimates 25 min 2 AvailabilityNines and downtime, single points of failure, redundancy in series and parallel 20 min 3 ScalingVertical and horizontal scaling, stateless services, sessions, auto scaling policies 25 min 4 Load balancingLayer 4 and layer 7 balancers, health checks, DNS routing policies, global routing 25 min 5 Caching and content deliveryCache-aside and write-through, TTL, invalidation, CDN edge caching 25 min 6 Databases at scaleRead replicas, multi-zone failover, partitioning and sharding, choosing by access pattern 25 min 7 Queues and eventsQueues, publish and subscribe, event buses, retries, dead-letter queues, idempotency 25 min 8 Monoliths, microservices and serverlessFunctions, API gateways, managed containers, service boundaries, when a monolith is right 25 min 9 Designing for failureTimeouts, retries with backoff, circuit breakers, graceful degradation, chaos testing 20 min 10 Disaster recoveryRPO and RTO, backup and restore, pilot light, warm standby, multi-site active-active 20 min 11 Security and network designDefence in depth, public and private tiers, encryption, key management, secrets, hybrid links 25 min 12 Cost, operations and reviewing a designCost trade-offs, observability, the six pillars, reviewing a design end to end 25 min 13 A photo app from a thousand users to a millionOne app grown a thousandfold: estimate, find the first limit, change only that, and set beside Instagram in 2011 Worked case25 min

Certifications

1 exam

When you have finished the lessons, take the exam course for the certification you want. This course teaches the subject to the depth of the hardest exam below; each exam course adds only what its exam asks on top: the vendor's own names, services and limits, and how the questions are built.

SAA-C03 AWS Certified Solutions ArchitectAWS · Associate · High Exam course coming

Professional exams later: SAP-C02, AZ-305, Google Professional Cloud Architect.

Sources and credit

51 sources

The chapters and drawings are written by NeuroqAI from these sources. Each lesson lists its own at the end of its chapter, and figures on the pages are taken from them or computed from them.

Amazon Web Services37 sourcesAWS Well-Architected FrameworkThe six pillars used to review any cloud designLessons 1, 12, 13AWS Certified Solutions Architect Associate (SAA-C03) exam guideThe domains of the associate architect examLessons 1, 12Reliability pillar (AWS Well-Architected)Availability arithmetic, fault isolation and static stabilityLessons 2, 9Amazon Compute Service Level AgreementWhat AWS promises for machines in one zone and across zonesLesson 2Multi-AZ deployments for Amazon RDSA standby in another zone, and how long failover takesLessons 2, 6Amazon EC2 instance typesThe families of virtual machines and what each is sized forLesson 3Amazon EC2 On-Demand pricingMachine prices per hour and data transfer pricesLessons 3, 12What is Amazon EC2 Auto Scaling?Groups of machines that grow and shrink with demandLesson 3What is an Application Load Balancer?Listener rules, target groups and health checksLesson 4What is Elastic Load Balancing?Application, network and gateway load balancersLesson 4Choosing a routing policy (Route 53)Weighted, latency, failover and geographic routingLesson 4Caching strategies (Amazon ElastiCache)Lazy loading, write-through and TTLLessons 5, 13What is Amazon CloudFront?Edge locations, cache keys and originsLessons 5, 13Working with DB instance read replicasAsynchronous copies that take readsLessons 6, 13What is Amazon Aurora?Six copies across three zones under one databaseLesson 6Partitions and data distribution (DynamoDB)Why the partition key decides how far a table scalesLesson 6What is Amazon Simple Queue Service?Queues that let one part of a system wait for anotherLesson 7What is Amazon SNS?One message delivered to many subscribersLesson 7What is Amazon EventBridge?Routing events by ruleLesson 7Understanding Lambda function scalingConcurrency is requests a second times durationLesson 8Lambda quotasThe limits of a function: 15 minutes, memory, payload and concurrencyLesson 8AWS Lambda pricingPrice per request and per GB-second, used for the cost barsLesson 8Exponential backoff and jitter (2015)The simulation behind adding randomness to retriesLesson 9Disaster recovery options in the cloudBackup and restore, pilot light, warm standby and multi-siteLesson 10Using Amazon Aurora Global DatabaseA copy in another region, about a second behindLesson 10Introduction to backups (Amazon RDS)Automated backups kept 1 to 35 days, and point-in-time restoreLesson 10Replicating objects (Amazon S3)Copies of a bucket in another regionLesson 10What is Amazon VPC?Private networks, subnets, route tables and gateways on AWSLesson 11Amazon VPC pricingNAT gateway hourly and per-GB prices used in the examplesLesson 11What is AWS PrivateLink?Reaching services without the internet or a NAT gatewayLesson 11AWS Key Management ServiceKeys that encrypt data, and who may use themLesson 11What is AWS Certificate Manager?Free certificates that renew themselvesLesson 11What is AWS Secrets Manager?Secrets stored, rotated and fetched at run timeLesson 11AWS WAFFiltering web requests before they reach the appLesson 11What is the AWS Well-Architected Tool?Running a review against the six pillarsLesson 12What are Savings Plans?A one- or three-year spend commitment in return for a lower rateLesson 12Amazon S3 storage classesEach S3 class, its retrieval time and what it is forLesson 12
Standards, research and other publishers14 sourcesISO/IEC 25010 quality model · ISO 25000 portalThe qualities a system can be asked to haveLesson 1Documenting architecture decisions (2011) · Michael NygardThe short decision record teams still useLesson 1Latency numbers every programmer should know, by year · Colin ScottJeff Dean's numbers, updated year by yearLesson 1The Tail at Scale (2013) · Jeffrey Dean and Luiz André BarrosoWhy the slowest 1% decides how fast a big system feelsLesson 1Embracing risk (Site Reliability Engineering) · GoogleError budgets: how much failure to allowLesson 2Service level objectives (Site Reliability Engineering) · GoogleSLIs, SLOs and SLAsLesson 2Service Level Agreements for Online Services · MicrosoftAzure's promised availability for each serviceLesson 2What are Virtual Machine Scale Sets? · MicrosoftAzure's groups of identical machines that scale out and inLesson 3RFC 9111: HTTP Caching · IETF (RFC Editor)Cache-Control, max-age and what a shared cache may keepLesson 5Microservices (2014) · James Lewis and Martin FowlerWhat the style is, and what it costsLesson 8Timeouts, retries and backoff with jitter · Amazon Builders' LibraryHow Amazon keeps retries from making outages worseLesson 9Using load shedding to avoid overload · Amazon Builders' LibraryRefuse some work to keep serving the restLesson 9Circuit breaker · Martin FowlerStop calling a service that is failingLesson 9What Powers Instagram: Hundreds of Instances, Dozens of Technologies · Instagram EngineeringThe whole stack at 14 million users, run by three engineersLesson 13