StreamHub started as one server. Today it runs through GeoDNS, a CDN, API gateway, stateless services, Redis, Postgres with read replicas, Kafka, and S3. This article maps the toolbox and shows where each piece fits.
The complete toolbox
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
| Block | Purpose | StreamHub usage |
|---|---|---|
| DNS / GeoDNS | Resolve hostname; route to nearest region | streamhub.com → US/EU/APAC clusters |
| CDN | Cache static and edge-cacheable content at PoPs | Video segments, thumbnails, JS bundles |
| Load balancer | Distribute traffic across app servers | ALB across EKS pods |
| API gateway | Auth, rate limiting, routing, TLS termination | Kong at edge; JWT validation |
| Cache (Redis) | Sub-ms reads for hot data | Stream metadata, sessions, rate limits |
| Database | Durable source of truth | Postgres primary + read replicas |
| Message queue | Async decoupling and spike absorption | Kafka events, RabbitMQ jobs |
| Object store | Blob storage for files and media | S3 for VOD, clips, profile images |
| Search index | Full-text and autocomplete queries | Elasticsearch for stream discovery |
DNS / GeoDNS
PurposeResolve hostname; route to nearest regionStreamHub usagestreamhub.com → US/EU/APAC clustersCDN
PurposeCache static and edge-cacheable content at PoPsStreamHub usageVideo segments, thumbnails, JS bundlesLoad balancer
PurposeDistribute traffic across app serversStreamHub usageALB across EKS podsAPI gateway
PurposeAuth, rate limiting, routing, TLS terminationStreamHub usageKong at edge; JWT validationCache (Redis)
PurposeSub-ms reads for hot dataStreamHub usageStream metadata, sessions, rate limitsDatabase
PurposeDurable source of truthStreamHub usagePostgres primary + read replicasMessage queue
PurposeAsync decoupling and spike absorptionStreamHub usageKafka events, RabbitMQ jobsObject store
PurposeBlob storage for files and mediaStreamHub usageS3 for VOD, clips, profile imagesSearch index
PurposeFull-text and autocomplete queriesStreamHub usageElasticsearch for stream discovery
How blocks connect
StreamHub production architecture (AWS)
Typical request path
- User resolves
streamhub.comvia DNS → GeoDNS routes to nearest region. - Static assets served from CDN edge; cache miss fetches from origin once.
- API requests hit load balancer → gateway (auth + rate limit) → app service.
- App reads Redis cache → Postgres on miss → publishes events to Kafka on writes.
- Media uploads go directly to S3 via presigned URLs; transcode workers pull from queue.
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 · 3 sections
- Growth stages
- Choosing blocks for a new feature
- Cross-cutting concerns
Test yourself
Answer these before moving on — recall is what makes it stick.