DynoTable @dynotable

The DynamoDB GUI with real SQL — joins, GROUP BY & aggregates, PartiQL, plus an AI agent on your own AWS. Local-first for Mac, Windows & Linux. dynotable.com Joined July 2026

Tweets

167
Followers

34
Following

676
Likes

69

DynoTable @dynotable

28 minutes ago

@astuyve @alexbdebrie That book is basically the shared vocabulary for DynamoDB at this point. Good sign the candidate reached for it unprompted.

0 0 0 10 0

View Details

DynoTable @dynotable

31 minutes ago

@martinhicks Scoring against the best-matching region instead of a pinned one is the fix that should’ve been obvious in hindsight and wasn’t. Nice work.

0 0 0 0 0

View Details

DynoTable @dynotable

6 hours ago

@awscloud Fund a support group for people who found a full-table Scan on their invoice.

0 0 0 2K 0

View Details

DynoTable @dynotable

7 hours ago

@yongfook Any verifiable problem will be eventually solved by llms. Design is not a verifiable problem. You can’t have a unit test for good UI

0 0 1 24 0

View Details

The “us-east-1 is not just another region” section deserves more attention than it gets. People pick a region for latency and never look at where the control planes actually live. One thing worth adding to the checklist: know which of your tables are Global Tables and which just look like they are. Wrote up the replication model and the last-writer-wins behavior here if useful: dynotable.com/learn/dynamodb…

0 0 0 2 0

View Details

DynoTable @dynotable

16 hours ago

@cherkaskyb @shar1z Zoom in on the legend, that’s RDS, not DynamoDB 😂 Though a real $1.5T Wednesday usually starts with a Scan nobody meant to run: dynotable.com/learn/dynamodb…

0 0 0 6 0

View Details

DynoTable @dynotable

16 hours ago

Because the modeling isn’t the hard part, the guessing is. You have to predict access patterns before you know your product. Bad ask for anything early stage. Start with a simple PK/SK, add GSIs when a real query forces you. Premature single-table design has burned more people than it’s saved: dynotable.com/learn/when-not…

0 0 1 7 0

View Details

DynoTable @dynotable

16 hours ago

@Nishanttt05 DynamoDB!

0 0 0 20 0

View Details

DynoTable @dynotable

17 hours ago

Do you know one DynamoDB partition key can hold a whole sorted collection? Add a sort key and related items live together, ordered, readable in a single Query. dynotable.com/learn/dynamodb…

0 0 0 18 0

View Details

DynoTable @dynotable

17 hours ago

@blog_nyanchu GSIのキースキーマ自体は変更できませんが、GSIを削除して新しいキーで作り直せます。どちらもUpdateTableのオンライン操作で、テーブル本体は止まりません。index変更は1回のUpdateTableにつき1つずつ。完全に不変なのはベーステーブルのPK/SKだけです。

0 0 0 7 0

View Details

DynoTable @dynotable

20 hours ago

The 24h Streams retention point is underrated. Pipeline breaks Friday night, you find out Monday, full rebuild. Worth checking first though: is the ask actually real-time, or is it “let me query this thing without writing expressions by hand”? dynotable.com is SQL over the table directly. Still Query and Scan underneath, just no pipeline to babysit.

0 0 1 8 0

View Details

DynoTable @dynotable

20 hours ago

@Taniyatweets_ pnpm all day, every day

0 0 0 13 0

View Details

DynoTable @dynotable

20 hours ago

@CodeByNZ Also unpopular opinion: you do actually need to know how to code in the first place to get anywhere further than localhost:3000

0 0 0 30 0

View Details

DynoTable @dynotable

a day ago

@shadcn Do you think Fable contributed to that model release? 😅

5 0 3 24K 0

View Details

DynoTable @dynotable

2 days ago

@broisnees Looks really cool 😎 Great job! Does it support DynamoDB?

1 0 0 53 0

View Details

DynoTable @dynotable

2 days ago

@kentcdodds True, this is why I built MCP server with oauth directly inside the app dynotable.com/blog/building-…

0 0 1 59 0

View Details

DynoTable @dynotable

2 days ago

Fair stack. KV for the app, cache in front, columnar for analytics. Covers a huge amount. Then someone asks for “users who did X then Y within 7 days, ranked by a friend’s score,” and you’re doing graph traversals and multi-way joins across three stores you’re now keeping in sync by hand. The three-store setup is great until the thing you’re building is the relationships between the data, not the data.

0 0 1 11 0

View Details

DynoTable @dynotable

2 days ago

An MCP server holding AWS credentials is a different problem than a toy stdio server. Safe meant OAuth inside a desktop app, scoped consent, a region pinned at approval. dynotable.com/blog/building-…

1 0 1 82 0

View Details

DynoTable @dynotable

2 days ago

@amritwt The pricing model is the difference. A hosted Postgres bills for the instance whether you use it or not. DynamoDB on-demand bills per request, so a low traffic app rounds to cents. The tradeoff: you commit to access patterns up front and ad hoc queries stop being free.

0 0 0 16 0

View Details

DynoTable @dynotable

2 days ago

@ignaziodes There is a query that settles it: sum ConsumedReadCapacityUnits and ConsumedWriteCapacityUnits over 30 days in CloudWatch, divide by what is provisioned. Tables everyone swears are steady usually idle nights and weekends. The metric ends the meeting.