| Category | Function | Share | Rank | Negative rate | Labels | Quadrant | Since September 2026 |
|---|---|---|---|---|---|---|---|
| NoSQL databases | Data platform | 11% | 2 of 73 | 21% | 67 | accepted challenger | ▼−1Since September 2026: 11% → 10%, −1 point. Inside the 11-point floor: within noise. Read over the models both editions asked. |
| Time series databases | Data platform | 0% | 24 of 66 | 0% | 1 | under 10 labels · led by TimescaleDB at 63% | |
| Vector databases | Data platform | 0% | 29 of 44 | 0% | 1 | under 10 labels · led by pgvector at 35% | newNew since September 2026: not ranked then, 0% now. |
| Category | September 2026 | Now | Change | Reading | Rank |
|---|---|---|---|---|---|
| NoSQL | 11% | 10% | ▼−1Since September 2026: 11% → 10%, −1 point. Inside the 11-point floor: within noise. Read over the models both editions asked. | Within noise | Rank 2 of 73, unchanged |
| Time series DBs | 0% | 0% | newNew since September 2026: not ranked then, 0% now. | New this edition | Rank 24 of 66, unchanged |
| Vector databases | 0% | 0% | newNew since September 2026: not ranked then, 0% now. | New this edition | Rank 29 of 44, unchanged |
Shares here are read over the models both editions asked, so they can differ by a point or two from the standing above, which counts every model in this edition.
The floor is 11 points of share, measured: how far the models move a leader on their own when the same questions are asked twice with nothing changed. A larger change is movement; a smaller one is noise, and both are shown. Movement is read over the twelve models both editions asked; GPT-6 Luna, Muse Glimmer 30B joined this edition and are in the standing but not yet in the comparison. How the floor is measured · The editions
| Model | First choice | Alternative | Mention | Negative | Labels |
|---|---|---|---|---|---|
| Claude Haiku 4.5 | 1 | 1 | 2 | 0 | 4 |
| GPT-5.4 mini | 0 | 2 | 3 | 0 | 5 |
| Gemini 3.5 Flash | 2 | 2 | 1 | 1 | 6 |
| Perplexity Sonar | 0 | 4 | 0 | 1 | 5 |
| Grok 4.20 | 1 | 1 | 1 | 2 | 5 |
| Mistral Small | 1 | 2 | 1 | 1 | 5 |
| DeepSeek V4 Flash | 0 | 4 | 0 | 1 | 5 |
| Llama 4 Maverick | 0 | 1 | 1 | 0 | 2 |
| Qwen 3.7 Flash | 0 | 3 | 2 | 0 | 5 |
| Kimi K2 | 0 | 2 | 1 | 4 | 7 |
| GLM 4.7 FlashX | 0 | 1 | 2 | 1 | 4 |
| MiniMax M2.5 | 0 | 3 | 1 | 1 | 5 |
| GPT-6 Luna | 0 | 4 | 1 | 1 | 6 |
| Muse Glimmer 30B | 2 | 2 | 0 | 1 | 5 |
Verbatim evidence the judge attached to positive labels.
“I'd typically recommend starting with a managed document database (MongoDB Atlas or DynamoDB) if you want flexibility” Claude Haiku 4.5 · NoSQL · paraphrase prompt · first choice
“DynamoDB is a pragmatic default because it gives you managed key-value performance with document-style JSON values” Muse Glimmer 30B · NoSQL · paraphrase prompt · first choice
“Amazon DynamoDB – #1 of 31 tools in a 2026 round-up, and listed as best managed key-value at scale” Muse Glimmer 30B · NoSQL · comparative prompt · first choice
“I want a $0/month bill to start and zero server maintenance | AWS DynamoDB or Firebase” Gemini 3.5 Flash · NoSQL · budget prompt · first choice
Verbatim evidence attached to negative labels. A warning on a product with few labels is a warning; on a product with many, it is one voice among them.
“Avoid DynamoDB as a primary application database unless your use case is a clean fit for key-value patterns” Kimi K2 · NoSQL · direct prompt · hard negative
“Avoid DynamoDB unless you are deeply invested in AWS” GLM 4.7 FlashX · NoSQL · paraphrase prompt · hard negative
“AWS guidance says to avoid large items, reads on non-key attributes, and scans, which means it can be a poor fit if your access pattern is not key-centric” Perplexity Sonar · NoSQL · negative prompt · soft negative
“many NoSQL databases (such as Amazon DynamoDB, Oracle NoSQL Database, or Couchbase) may be more complex and costly than traditional SQL databases” Mistral Small · NoSQL · negative prompt · soft negative
Citations exist only for the models that return a source list, five of the fourteen in this edition, so these counts come from 155 of the 188 answers that named Amazon DynamoDB and are not a share of its labels.
384 of the 424 domain citations in answers naming Amazon DynamoDB came from somebody else's page.
Pages are listed as the models cited them.
Search figures are US estimates from DataForSEO, read September 28, 2026; AI search demand is its modeled, directional estimate, not a count of queries to any assistant. The answers are this edition's. Two measurements side by side: neither is read as the cause of the other.
| Kind | Pages | Last 90 days | 2025-10 to 2026-09 | Latest | Categories named |
|---|---|---|---|---|---|
| Blog | 27,117 | undated | API gateways, ETL | ||
| Glossary or explainer | 6,521 | undated | ETL, MFA | ||
| Case study | 2,476 | 0 | 2019-03-01 | WAF, Observability | |
| Webinar or virtual event | 2,057 | 16 | 2026-07-01 | Streaming, API gateways | |
| Comparison | 1,521 | 0 | 2025-09-01 | Object storage, ETL | |
| Conference or event | 1,482 | 0 | 2025-11-01 | Vector databases | |
| Report or ebook | 1,090 | 16 | 2026-09-01 | WAF, NoSQL | |
| Podcast or video | 351 | undated | ETL | ||
| Template or tool | 150 | 0 | 2025-05-01 | ||
| News or press | 34 | undated |
As the event pages on aws.amazon.com state them, read September 28, 2026.
Every page aws.amazon.com exposes, subdomains included. Kind is read from the address and title. The last 90 days, the latest date and the twelve months count pages by when they were published, from the site's feeds, a date in the address, or the page's own publication date, read from up to a hundred of its most recently changed pages; a page that says only when it last changed is counted in its kind but not in when, so the recent counts are a floor, and a kind none of whose pages gives a publication date reads undated. Of its titles that name a category, most name ETL (168); 0 name its categories the models place it in. An event counts as online when its address or title says so (webinar, on demand, virtual or online summit); a conference, summit, trade show, expo or roadshow that does not say so is counted as a conference or event, which on a vendor's site is mostly in person. Read September 28, 2026.
An email the morning each edition publishes: where this product moved, where it held, and by how much against the noise floor. One address, confirmed by a click; a stop link in every email.
Already following? Everything you follow, with a stop for each.
Claiming is free and changes nothing in the data. A claimed page shows a verified contact who is told when each edition publishes and when Amazon DynamoDB's standing changes by more than the noise floor; the right to propose corrections to the vendor table, meaning names the judge wrote that should or should not read as Amazon DynamoDB, applied by version and listed in the change log; and a one-line description supplied by the vendor and marked as such.
A new claim receives the current edition's vendor brief for Amazon DynamoDB by email, built from the raw record of the edition. It shows:
Amazon DynamoDB is among the products AI models recommend first in NoSQL databases this edition. Each badge says so in the buyer's words, names the edition, and links to the standing. The next edition issues a new badge; this one stays true as a record of October 2026.
Badges read on light and dark pages. Alt text carries the claim, the category, the edition and the index, so it stays a citation where the image does not load.