Softwr

Databases · head to head

DynamoDB vs Mollie

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

Mollie

E-Commerce

European payment service provider with published per-transaction rates and no monthly fee on the online plan

From
£0.3/transaction
Free plan
No

The short version

  • DynamoDB has a free plan, then $0.625/mo; Mollie starts at £0.3/mo.
  • Only DynamoDB lists managed and serverless; only Mollie lists local payment methods.
  • Prices and features on this page were last checked on 13 November 2026.

Where they differ

Only the attributes on which DynamoDB and Mollie actually diverge.

Attributes where DynamoDB and Mollie differ
AttributeDynamoDBMollie
Starting priceFree£0.3/transaction
Pricing modelUsage-basedPer transaction by payment method
Free tierYesNo
PlatformsAWSWeb, iOS, Android, API
CategoryDatabasesE-Commerce

Not yet recorded: founded for Mollie.

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 Mollie

  • Local payment methods
  • Published rate card
  • Hosted checkout and payment links
  • Subscriptions API
  • Point of sale terminals
  • Plugin ecosystem
  • Multicurrency settlement

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

Mollie

  • A Dutch or Belgian shop where most customers pay by iDEAL or Bancontact and the flat 30p beats a percentage rate on high-value basketsnot DynamoDB
  • A small merchant that wants published pricing rather than a sales call before it can model card costsnot DynamoDB
  • A subscription business in the EEA collecting by SEPA Direct Debit mandate instead of cardnot DynamoDB
  • A marketplace or platform that needs one integration covering the main European local methodsnot 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

Mollie

  • Non-European cards cost 3.25% plus 20p against 1.20% plus 20p for UK domestic consumer cards, so a merchant with significant traffic from the US or Asia pays close to triple the domestic rate on that revenue
  • Coverage is built around European methods, so if you expand into Latin America or Southeast Asia you will need a second processor and a second reconciliation process rather than extending Mollie
  • The in-person Pro plan requires a one-year contract and charges 20 pounds a month per additional terminal, so a shop with four tills pays 80 pounds a month in terminal fees before any transaction cost
  • Mollie offers no interchange-plus option publicly, so large merchants cannot see or benefit from falling interchange the way they could on a cost-plus contract with an acquirer
  • The developer tooling and reporting are lighter than the largest processors, so finance teams that want detailed fee breakdowns or granular reconciliation exports often end up building that layer themselves

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

Mollie

£0.3/transaction
  • Online paymentsFree
    • No monthly fee
    • UK domestic consumer cards 1.20% + 20p
    • European and commercial cards 2.90% + 20p
  • In person, pay as you goFree
    • No monthly commitment
    • Per-transaction terminal rates
    • One terminal
  • In person, Pro£20/mo
    • Lower per-transaction terminal rates
    • One-year contract required
    • Each additional terminal 20 pounds per month

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

  • You need local payment methods.
  • You work on Web, iOS, Android, API.
  • You also want published rate card.

Questions people ask

Is DynamoDB or Mollie better?
Neither clearly leads. DynamoDB starts at Free and Mollie at £0.3/transaction, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, DynamoDB or Mollie?
DynamoDB has a free tier; the other does not. Paid plans start at Free for DynamoDB and £0.3/transaction for Mollie.
Does DynamoDB or Mollie run on more platforms?
DynamoDB runs on AWS. Mollie runs on Web, iOS, Android, API.
Can I use DynamoDB for free?
Yes. DynamoDB has a free tier, so you can try it without paying. Mollie starts at £0.3/transaction.
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 Mollie is typically brought in for.
What can DynamoDB do that Mollie cannot?
DynamoDB covers Managed and serverless, Predictable latency, On-demand or provisioned capacity, Global secondary indexes. Mollie covers Local payment methods, Published rate card, Hosted checkout and payment links, Subscriptions API.

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.

Mollie: Does Mollie charge a monthly fee?

Not on the online payments plan. You pay only per successful transaction. In-person Pro is 20 pounds a month.

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.

Mollie: Is iDEAL really a flat fee?

Yes, 30p per transaction regardless of the amount, which is why it is cheaper than cards on high-value baskets.

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.

Mollie: Can I use Mollie outside Europe?

You can accept non-European cards but at 3.25% plus 20p, and merchant accounts are aimed at European businesses. It is not a global processor.

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.

Mollie: Does Mollie do interchange plus?

Not publicly. The published rates are blended, so falling interchange does not flow through to you automatically.

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