Blog
AWS, Azure and Google Cloud, Compared From the Docs
How the three big clouds map to each other, how each service bills, and what each vendor retires and when. Every page names the vendor documents it was checked against.
AWS, Azure and Google Cloud sell services that look alike and behave differently. A queue on one cloud can guarantee something that the same-looking service on another does not, and two NAT gateways can bill for different things. The notes here take one trio of services at a time and compare the mechanism that decides the outcome: limits, how billing is metered, delivery guarantees and what happens when a service sits idle.
Every number is taken from the vendor's own documentation, fetched on the date shown in each page's Sources list. Quotas change, so check the vendor page before you rely on a figure. These pages compare documents. They are not benchmarks, and they do not replace a test in your own account.
Service equivalents
2026-11-19
SQS vs Service Bus vs Pub/Sub: Delivery Guarantees Compared
The three services put their guarantees in different places. SQS FIFO orders per message group and deduplicates for 5 minutes. Service Bus orders through sessions and detects duplicates by MessageId over a window you set. Pub/Sub orders per key on subscriptions created for it and offers exactly-once delivery only on pull subscriptions, within one region.
Read2026-11-19
Fargate vs Container Apps vs Cloud Run: Idle and Scale to Zero
Cloud Run and Container Apps scale to zero by default, and neither bills compute at zero. Fargate scales to zero only if you set the ECS minimum capacity to 0. Each also meters idle capacity differently and has its own request timeout and concurrency control, so check those before you port a workload.
Read2026-11-19
Cognito vs Entra External ID vs Google Identity Platform
The three products differ in what you create and what you can tune. Cognito gives you regional user pools with token lifetimes set per app client. External ID uses a separate external tenant, with access-token lifetime set through Microsoft Graph. Identity Platform keeps users in a project, with tenants as an option. Triggers, MFA and migration paths differ too.
ReadHow services bill
2026-11-19
AWS NAT Gateway vs Azure NAT Gateway vs Cloud NAT: What Each Bills
All three bill an hourly gateway charge plus data processed, but they count the hour differently. AWS bills each gateway-hour, and a regional gateway bills per Availability Zone. Azure bills from creation, whatever is attached. Google bills per VM using the gateway, capped at 32. Public IP addresses and ordinary data transfer are billed on top.
Read2026-11-19
Lambda vs Azure Functions vs Cloud Run Functions: Limits and What Each Bills
The three services differ most in how many requests one instance handles at a time and in what they meter. Lambda event functions run one request per environment and bill requests plus duration. Azure Flex Consumption runs several per instance. Cloud Run functions document up to 1,000 per instance and bill as Cloud Run services.
Read2026-11-19
DynamoDB vs Cosmos DB vs Firestore: How Each Meters Reads and Writes
The three meter different things. DynamoDB meters item size, in 4 KB units for reads and 1 KB units for writes. Cosmos DB meters work in request units, where size, indexing and some consistency levels change the charge. Firestore Standard counts documents and index entries read, and its pricing page names no size tranche.
ReadNext step
Have a project in mind?
Tell me about it. A discovery call within 48 hours.