Softwr

APIs · head to head

AWS API Gateway vs DynamoDB

AWS API Gateway logo

AWS API Gateway

APIs

Fully managed API gateway service for creating and managing APIs at scale

From
Free
Rated
-
DynamoDB logo

DynamoDB

Databases

AWS-only managed key-value and document database with fixed per-partition throughput limits and no ad hoc queries.

From
Free
Rated
-

The short version

  • Each has a real cost: AWS API Gateway rEST APIs cost $3.50 per million calls against $1.00 for HTTP APIs, so the older and more featureful type is three and a half times dearer; DynamoDB access patterns must be designed into the key schema before launch; a query nobody anticipated needs a new global secondary index, which is a full extra copy of the projected attributes billed as storage and as writes, or an offline migration.
  • They diverge on capability: AWS API Gateway covers REST APIs, DynamoDB covers Managed and serverless.
  • Prices and features above were last checked on 30 August 2026.

Where they differ

Only the attributes on which AWS API Gateway and DynamoDB actually diverge.

Attributes where AWS API Gateway and DynamoDB differ
AttributeAWS API GatewayDynamoDB
PlatformsAWS CloudAWS
CategoryAPIsDatabases

Identical on both: starting price (Free), pricing model (usage-based), free tier (Yes), user rating (Not yet rated), founded (2006).

What each one covers

Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.

Only in AWS API Gateway

  • REST APIs
  • WebSocket APIs
  • HTTP APIs
  • Lambda
  • EC2
  • DynamoDB
  • CloudWatch
  • IAM

Only in DynamoDB

  • Managed and serverless
  • Predictable latency
  • On-demand or provisioned capacity
  • Global secondary indexes
  • Transactions
  • DynamoDB Streams
  • Global tables
  • Point-in-time recovery

What people use each for

The jobs each tool is most often brought in to do.

AWS API Gateway

  • Fronting Lambda functions with an HTTP endpointnot DynamoDB
  • REST and HTTP API management with throttling and keysnot DynamoDB
  • WebSocket APIs for real-time clientsnot DynamoDB
  • Private APIs reachable only inside a VPCnot DynamoDB
  • Publishing a developer portal for API consumersnot DynamoDB

DynamoDB

  • High-volume keyed workloads such as sessions, shopping carts, device state or user profiles where the access pattern is fixed and knownnot AWS API Gateway
  • Traffic that spikes unpredictably, where on-demand capacity absorbs a burst without a capacity-planning exercisenot AWS API Gateway
  • Serverless applications on Lambda, where an HTTP-based datastore avoids the connection pooling problem relational databases havenot AWS API Gateway
  • Event or telemetry ingestion where writes vastly outnumber reads and each record is retrieved by a known identifiernot AWS API Gateway

Where each one falls short

Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

AWS API Gateway

  • REST APIs cost $3.50 per million calls against $1.00 for HTTP APIs, so the older and more featureful type is three and a half times dearer
  • Data transfer out is charged at $0.09 per GB on top of request pricing
  • WebSocket APIs bill connection minutes as well as messages, at $0.25 per million minutes
  • Private APIs avoid data transfer charges but incur AWS PrivateLink costs instead
  • The developer portal is $125 a month, with additional portal products at $12.50 each
  • The free tier lasts 12 months rather than being ongoing

DynamoDB

  • Access patterns must be designed into the key schema before launch; a query nobody anticipated needs a new global secondary index, which is a full extra copy of the projected attributes billed as storage and as writes, or an offline migration.
  • Global secondary indexes are eventually consistent and cannot be read strongly, so a read-after-write against an index can legitimately miss the item that was just written, and application code must be written to tolerate that.
  • Per-partition throughput is capped at roughly 3,000 read and 1,000 write units, so a hot key throttles even when the table has spare capacity overall, and the only real fix is changing the key design to spread the load.
  • Items are limited to 400 KB and query results paginate at 1 MB, so large or list-shaped data has to be split, offloaded to S3 with a pointer, or read through pagination loops that complicate every consumer.
  • It runs only on AWS and the API is proprietary rather than a standard, so moving the data layer means rewriting it; ScyllaDB's Alternator is the only meaningfully compatible target and it brings a much smaller ecosystem.

Pricing, plan by plan

AWS API Gateway

Free
  • Free Tier (12 months)Free
    • 1M REST API calls per month
    • 1M HTTP API calls per month
    • 1M WebSocket messages plus 750K connection minutes per month
  • HTTP APIs$1/per million requests (first 300M)
    • First 300M: $1.00 per million
    • Next 132M: $0.90 per million
    • Data transfer varies by volume
  • REST APIs$3.5/per million API calls
    • Edge Optimized and Regional: $3.50 per million (first tier)
    • Higher volumes: $2.80 then $2.38 per million
    • Data transfer: $0.09 per GB
  • WebSocket APIs$1/per million messages
    • Messages: $1.00 per million
    • Connection minutes: $0.25 per million minutes

DynamoDB

Free
  • On-Demand Capacity$null/usage-based
    • Pay-per-request pricing with automatic scaling
    • Read: 0.5 RRU per 4 KB (eventually consistent), 1 RRU per 4 KB (strongly consistent), 2 RRU per 4 KB (transactional)
    • Write: 1 WRU per 1 KB
  • Provisioned Capacity$null/hourly
    • Fixed hourly charges based on reserved capacity
    • RCU rate: $0.00013 per hour (Standard)
    • WCU rate: $0.00065 per hour (Standard)
  • Standard Table Class Storage$0.25/per GB/month
    • $0.25 per GB/month after free tier
    • First 25 GB free per month (free tier)
  • Standard-Infrequent Access Table Class$0.1/per GB/month
    • $0.10 per GB/month

Which should you pick?

Choose AWS API Gateway if

  • You need rest apis.
  • You want to start without paying.
  • You work on AWS Cloud.
  • You also want websocket apis.

Choose DynamoDB if

  • You need managed and serverless.
  • You want to start without paying.
  • You work on AWS.
  • You also want predictable latency.

Questions people ask

Is AWS API Gateway or DynamoDB better?
Neither clearly leads. AWS API Gateway starts at Free and DynamoDB at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, AWS API Gateway or DynamoDB?
AWS API Gateway starts at Free and DynamoDB at Free.
Does AWS API Gateway or DynamoDB run on more platforms?
AWS API Gateway runs on AWS Cloud. DynamoDB runs on AWS.
Can I use AWS API Gateway for free?
Both have a free tier, so you can try either at no cost before committing.
What is AWS API Gateway best used for?
AWS API Gateway is most often used for fronting lambda functions with an http endpoint, rest and http api management with throttling and keys, websocket apis for real-time clients, private apis reachable only inside a vpc. Of those, fronting lambda functions with an http endpoint and rest and http api management with throttling and keys are not what DynamoDB is typically brought in for.
What can AWS API Gateway do that DynamoDB cannot?
AWS API Gateway covers REST APIs, WebSocket APIs, HTTP APIs, Lambda. DynamoDB covers Managed and serverless, Predictable latency, On-demand or provisioned capacity, Global secondary indexes.

Answered from the vendors’ own pages

AWS API Gateway: How much does AWS API Gateway cost?

AWS API Gateway pricing varies by API type. HTTP APIs cost $1.00 per million requests for the first 300M monthly, then $0.90 per million. REST APIs cost $3.50 per million, and WebSocket APIs cost $1.00 per million messages plus $0.25 per million connection minutes. Data transfer charges ($0.09 per GB) apply separately.

Source
DynamoDB: On-demand or provisioned capacity?

On-demand suits unpredictable or spiky traffic and removes capacity planning. Provisioned with autoscaling is considerably cheaper for steady high-volume workloads. Tables can be switched between them, though not arbitrarily often.

AWS API Gateway: Is AWS API Gateway free?

New AWS customers receive 12 months of free tier access including 1 million REST API calls, 1 million HTTP API calls, and 1 million WebSocket messages plus 750,000 connection minutes per month. Starting July 15, 2025, new customers receive up to $200 in AWS Free Tier credits.

Source
DynamoDB: Can I run DynamoDB outside AWS?

No. DynamoDB Local exists for development and testing only. For a production-compatible alternative elsewhere, ScyllaDB's Alternator implements the DynamoDB API, but it is a different system with a different ecosystem.

AWS API Gateway: What is the price difference between HTTP and REST APIs?

HTTP APIs are significantly cheaper at $1.00 per million requests compared to REST APIs at $3.50 per million (first tier). REST API pricing decreases to $2.80 and $2.38 per million for higher volumes, while HTTP API pricing drops to $0.90 per million after 300M monthly requests.

Source
DynamoDB: Can I run ad hoc queries or analytics?

Not on the table itself. Scans are slow and expensive at scale. The usual pattern is to export to S3 or stream changes out and query them in Athena, Redshift or another analytical engine.

AWS API Gateway: How much does an API Gateway Portal cost?

API Gateway Portals require a base fee of $125 per month (includes 10 PortalProducts with 40 endpoints each) plus $12.50 per month for each additional PortalProduct beyond the included 10.

Source
DynamoDB: Is single-table design necessary?

It is the pattern that gets the most from DynamoDB when access patterns are well known, because it lets related items be retrieved in one query. It also makes the model harder to evolve, so many teams reasonably choose multiple simpler tables and accept extra requests.

DynamoDB: What are the real limits I should design around?

400 KB per item, 1 MB per query or scan page, 100 items per transaction, roughly 3,000 read and 1,000 write units per partition, and eventual consistency on global secondary indexes.

Share

Related pages

Other head to heads