Why this matters
- Single-page review before VaultCommerce loop or external interviews.
- Covers what interviewers probe at staff level: EOS, KRaft, partitioning, ops.
- Cross-links mental models from all 51 prior articles.
- Not a substitute for depth — a structured recall aid.
Cloud building blocks toolbox
NETWORKRoute 53DNS + GeoDNS
NETWORKCloudFrontCDN edge
NETWORKAWS ALBL7 balance
NETWORKAPI Gatewayauth + throttle
COMPUTEAmazon EKScontainer fleet
DATABASEElastiCacheRedis cache
DATABASERDS / Aurorarelational
DATABASEDynamoDBkey-value
INTEGRATIONMSK / SQSasync events
STORAGEAmazon S3object store
ANALYTICSOpenSearchfull-text
OPSCloudWatchmetrics · logs
SECURITYAWS WAFedge security
SECURITYCognitoidentity
COMPUTELambdaserverless
INTEGRATIONSNS / SESnotify
Architecture quick reference
Broker hosts partition leaders. Topic → partitions → ordered offsets. Consumer groups divide partitions. KRaft controllers manage metadata. RF=3, min.insync.replicas=2, acks=all for durability. VaultCommerce baseline cluster: 6 brokers, 12 partitions on order topics.
Key points
- KRaft — metadata quorum; no ZooKeeper
- ISR + acks=all — durable produce path
- Partition key — ordering scope
- Consumer lag — primary consumer health metric
- Transactional outbox — DB-Kafka consistency pattern
The rest of this guide is part of Pro
Free covers every fresher guide in full. Pro unlocks Senior, Staff and Architect guides across every track.
Still to come · 2 sections
- Semantics and patterns
- Tuning and ops knobs
Test yourself
Answer these before moving on — recall is what makes it stick.