Softwr

Databases · head to head

DynamoDB vs eBay

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
Free plan
Yes
E

eBay

E-Commerce

Global marketplace where sellers list into eBay's audience under eBay's fee schedule and rules

From
On request
Free plan
No

The short version

  • DynamoDB starts at $0.625/mo; eBay prices on request.
  • Only DynamoDB lists predictable latency; only eBay lists auction and fixed price listings.
  • Prices and features on this page were last checked on 13 November 2026.

Where they differ

Only the attributes on which DynamoDB and eBay actually diverge.

Attributes where DynamoDB and eBay differ
AttributeDynamoDBeBay
Starting priceFreeOn request
Pricing modelUsage-basedSubscription
Free tierYesNo
PlatformsAWSWeb
CategoryDatabasesE-Commerce

Not yet recorded: founded for eBay.

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 DynamoDB

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

Only in eBay

  • Auction and fixed price listings
  • Managed payments
  • eBay Stores
  • Promoted Listings
  • Bulk listing tools
  • International selling programmes
  • Money Back Guarantee
  • Seller performance standards

What people use each for

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

DynamoDB

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

eBay

  • Selling used, refurbished or one-off stock that has no natural search demand on its own sitenot DynamoDB
  • Parts and spares catalogues where buyers search by fitment rather than by brandnot DynamoDB
  • Liquidating returns or excess inventory without building an audience for itnot DynamoDB
  • Testing whether demand exists for a product line before investing in a standalone storefrontnot DynamoDB

Where each one falls short

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

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

eBay

  • The final value fee applies to the total the buyer pays including postage and tax rather than to the item price, so a low value item with expensive shipping loses a much larger share of its margin than the headline percentage implies
  • Fees stack rather than substitute, since a Store subscription, a per order fixed fee, Promoted Listings and cross-border percentages all apply on top of the category rate, and the effective take rate is only visible after a full month of settlement reports
  • eBay controls search placement, so as a category gets competitive the practical cost of visibility becomes the Promoted Listings rate, and that is an auction against other sellers that only goes one way
  • You do not get the customer relationship, because eBay mediates messaging and does not supply a marketing list, so repeat business depends on eBay showing your listing again rather than on anything you own
  • The account is the entire asset and it is governed by policies eBay enforces unilaterally, so a suspension or a category restriction ends the revenue immediately with no portable equivalent of a domain, a theme or a customer database to move elsewhere

Pricing, plan by plan

DynamoDB

Free
  • On-Demand CapacityOn request
    • 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 CapacityOn request
    • 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

eBay

On request

No published plan breakdown. See the eBay review.

Which should you pick?

Choose DynamoDB if

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

Choose eBay if

  • You need auction and fixed price listings.
  • You also want managed payments.

Questions people ask

Is DynamoDB or eBay better?
Neither clearly leads. DynamoDB starts at Free and eBay at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, DynamoDB or eBay?
DynamoDB has a free tier; the other does not. Paid plans start at Free for DynamoDB and On request for eBay.
Does DynamoDB or eBay run on more platforms?
DynamoDB runs on AWS. eBay runs on Web.
Can I use DynamoDB for free?
Yes. DynamoDB has a free tier, so you can try it without paying. eBay starts at On request.
What is DynamoDB best used for?
DynamoDB is most often used for high-volume keyed workloads such as sessions, shopping carts, device state or user profiles where the access pattern is fixed and known, traffic that spikes unpredictably, where on-demand capacity absorbs a burst without a capacity-planning exercise, serverless applications on lambda, where an http-based datastore avoids the connection pooling problem relational databases have, event or telemetry ingestion where writes vastly outnumber reads and each record is retrieved by a known identifier. Of those, high-volume keyed workloads such as sessions, shopping carts, device state or user profiles where the access pattern is fixed and known and traffic that spikes unpredictably, where on-demand capacity absorbs a burst without a capacity-planning exercise are not what eBay is typically brought in for.
What can DynamoDB do that eBay cannot?
DynamoDB covers Managed and serverless, Predictable latency, On-demand or provisioned capacity, Global secondary indexes. eBay covers Auction and fixed price listings, Managed payments, eBay Stores, Promoted Listings.

Answered from the vendors’ own pages

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.

eBay: What does selling on eBay actually cost?

A category-dependent percentage of the total buyer payment including postage, plus a fixed fee per order, plus any Store subscription, advertising rate and international fees. Model all of them together, not the first one alone.

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.

eBay: Can I use my own payment provider?

No. Payments run through eBay and settle to your bank account on eBay's payout schedule, so you do not choose the processor and you do not control settlement timing.

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.

eBay: Do I get my customers' email addresses?

Not for marketing. eBay mediates buyer contact, which is why sellers who rely on it have no list to fall back on if the channel changes.

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.

eBay: Is eBay an alternative to having my own store?

It is a channel, not a substitute. Sellers who use it well treat it as demand they rent while building something they own in parallel.

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