All posts
Data Platform

Reading Your Own Writes in DynamoDB: A Secondary Index Was Stale 90% of the Time

By

November 9, 2026

6 min read

Right after writing an item, a query on a global secondary index didn't find it in 269 of 300 tries. Secondary indexes are eventually consistent, and "eventually" was longer than one request. What that means for "save, then show the list" screens, what strong consistency costs, and how long adding a new index took.

Benchmark
Postgres Performance
DynamoDB
Consistency

Write, then immediately read

Found the new item

DynamoDB, query on a global secondary index

31 of 300 (10%)

Postgres, query on a secondary index

300 of 300

Our measurements, November 2026.

The full report has the method, what strongly consistent reads cost (twice the read units, no faster), why consistent reads aren't available on global secondary indexes at all, the transaction latency, and what happened when we added a new secondary index to a million-item table.

Users seeing stale lists after saving?

We'll go through the read paths with you and fix the ones that matter. 30 minutes, free.

hoolco Monthly Review

Once a month: what changed in tech that month and what it means for you, from cloud and AI to security and the tools you build with. Every item links to its source. No sales pitch, unsubscribe in one click.

As of November 9, 2026. Provided as is, for general information, and accurate to the best of our knowledge on the date shown. Not legal, compliance, tax, financial or other professional advice. Prices, limits and vendor services change; check current vendor documentation before relying on anything here. Terms of use.