Tagged
AWS IoT architecture patterns for manufacturing, smart buildings, and connected devices — from device connectivity to data ingestion, edge processing with Greengrass, and real-time analytics.
A technical guide to hybrid compute architectures that combine EC2, Lambda, Fargate, and Step Functions — with worked cost calculations, SQS buffering patterns, and decision frameworks based on invocation pattern rather than unit cost.
SQS is "reliable" only if you understand visibility timeout, dead-letter queues, and the silent failure mode where messages get processed twice. Standard vs FIFO, DLQ tuning, Lambda integration, and the patterns that turn SQS from "queue with default settings" into reliable backbone messaging.
July 2026 decision guide: monolith → modular monolith → microservices on AWS — team size, platform tax (VPC Lattice/mesh), and a checklist before you split for the org chart.
Three API types, three pricing models, three authentication patterns — and the wrong choice baked into your URL design for years. A decision guide for picking REST vs HTTP vs WebSocket APIs, with the throttling and caching configs that decide your monthly bill.
July 2026: Cognito user pools for SaaS — managed login vs classic hosted UI, pool vs silo tenancy, federation limits, and a checklist before you outgrow Cognito into Auth0/Okta.
Event-driven sounds elegant in design docs. Then a malformed event ships to a critical bus and you spend a weekend debugging fan-out. EventBridge buses, rules, schema discovery, cross-account patterns, and the failure modes you only learn about in production.
Fintech on AWS isn't about more services — it's about which services you're allowed to use, how you isolate customer funds, and how fast your audit trail responds. Architecture patterns for payments, fraud detection, regulatory compliance, and the AWS primitives that power modern financial platforms.
July 2026: EdTech serverless on AWS — exam-day spikes, SQS grading buffers, CloudFront video egress, and a readiness checklist so load tests match Monday 9am reality.
Step Functions is the AWS service most teams under-use until they need it badly. Patterns for sequential pipelines, parallel fan-out, error handling, human approval workflows, and the cost optimisations that keep state-transition bills predictable.
Single-table design is either DynamoDB's superpower or a six-month rewrite waiting to happen. SaaS access patterns, tenant isolation, GSI strategies, and the patterns that make DynamoDB the right serverless database for multi-tenant apps — plus the patterns that get teams in trouble.
Provisioned Concurrency is still the most over-bought Lambda knob. July 2026: INIT billed since Aug 2025, SnapStart runtimes, ~$54/mo illustrative PC baseline math, Power Tuning before you buy warm capacity.