Softwr

Databases · head to head

DynamoDB vs Mercari

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
Mercari logo

Mercari

E-Commerce

Japan-founded peer-to-peer resale marketplace with a flat seller commission

From
Free
Free plan
Yes

The short version

  • Mercari is free; DynamoDB starts at $0.625/mo.
  • Only DynamoDB lists managed and serverless; only Mercari lists flat seller commission.
  • Prices and features on this page were last checked on 13 November 2026.

Where they differ

Only the attributes on which DynamoDB and Mercari actually diverge.

Attributes where DynamoDB and Mercari differ
AttributeDynamoDBMercari
Pricing modelUsage-basedFree to list; 10 percent seller commission on sale price plus payment processing fee
PlatformsAWSiOS, Android, Web
CategoryDatabasesE-Commerce

Identical on both: starting price (Free), free tier (Yes).

Not yet recorded: founded for Mercari.

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 Mercari

  • Flat seller commission
  • Prepaid shipping labels
  • Local pickup and offers
  • Smart pricing and price drops
  • Mercari authenticity guarantee
  • Instant or standard payout

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 Mercari
  • Traffic that spikes unpredictably, where on-demand capacity absorbs a burst without a capacity-planning exercisenot Mercari
  • Serverless applications on Lambda, where an HTTP-based datastore avoids the connection pooling problem relational databases havenot Mercari
  • Event or telemetry ingestion where writes vastly outnumber reads and each record is retrieved by a known identifiernot Mercari

Mercari

  • Someone clearing out a wide mix of household items, not just clothing, in one listing appnot DynamoDB
  • A casual seller who wants a flat, predictable commission rather than a tiered fee structurenot DynamoDB
  • A buyer looking for secondhand electronics or general goods alongside apparelnot DynamoDB
  • A seller using local pickup to avoid shipping costs on bulky itemsnot 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

Mercari

  • The flat 10 percent commission plus payment processing fees applies even to very low-value items, so selling something for a few dollars can leave the seller with proportionally little after fees and packaging
  • Shipping is the seller's responsibility to arrange and package correctly, and disputes over item condition or damage in transit are common friction points in buyer-seller resolution
  • Instant payout carries its own fee on top of the selling and processing fees already deducted, so getting money out quickly costs more than waiting for standard transfer
  • Buyer protection and authenticity verification are limited outside the specific luxury authentication programme, so counterfeit risk on unverified categories rests largely on buyer judgement of listing photos and seller ratings
  • Market depth and typical sale prices vary significantly between the Japan and US versions of the app, and the two operate as largely separate marketplaces despite the shared brand

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

Mercari

Free
  • SellingFree
    • 10 percent selling fee on final sale price
    • Separate payment processing fee, roughly 2.9 percent plus a fixed amount
    • Instant payout carries an additional fee versus standard bank transfer

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 Mercari if

  • You need flat seller commission.
  • You want to start without paying.
  • You work on iOS, Android, Web.
  • You also want prepaid shipping labels.

Questions people ask

Is DynamoDB or Mercari better?
Neither clearly leads. DynamoDB starts at Free and Mercari at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, DynamoDB or Mercari?
DynamoDB starts at Free and Mercari at Free.
Does DynamoDB or Mercari run on more platforms?
DynamoDB runs on AWS. Mercari runs on iOS, Android, Web.
Can I use DynamoDB for free?
Both have a free tier, so you can try either at no cost before committing.
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 Mercari is typically brought in for.
What can DynamoDB do that Mercari cannot?
DynamoDB covers Managed and serverless, Predictable latency, On-demand or provisioned capacity, Global secondary indexes. Mercari covers Flat seller commission, Prepaid shipping labels, Local pickup and offers, Smart pricing and price drops.

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.

Mercari: How much does Mercari charge sellers?

A flat 10 percent selling fee on the final sale price in the US, plus a separate payment processing fee, both deducted from the seller payout.

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.

Mercari: Does the buyer pay any extra platform fee?

No separate platform fee is added at buyer checkout the way Vinted adds a buyer protection fee; the buyer pays the listed price plus shipping if not included.

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.

Mercari: Is Mercari the same marketplace in Japan and the US?

No, they operate as separate marketplaces under the same brand, with different inventory, pricing and fee history.

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