DynoTable

Meet DynoTable — a fast desktop GUI for AWS DynamoDB. Open a table, filter with autocomplete, edit a row, commit. It runs on your machine and talks straight to AWS — your data never touches our servers. Here's what it does.

@anupamrjp dynotable.com

Built something you’re excited about? Promote your project URL Tell everyone what it does in one sentence. You might find your next user, customer, collaborator, or biggest supporter in this thread.

@lightsilver323 dynotable.com

Built something you’re proud of? Drop your project URL

This is the plan-level version of a problem we hit at the execution level. An agent that redesigns instead of evaluates is annoying in a chat; one holding your AWS credentials, it’s an incident. Our conclusion was the same as yours, just enforced in architecture: assume the agent is confused at best. dynotable.com/blog/building-…

*When AI Solves a Better Problem Than Yours* The most dangerous suggestion isn't wrong. It's a working solution you'd still regret shipping. I was designing a sync system for my privacy focused app Gepeta. After several rounds, we arrived at an elegant DynamoDB architecture: the primary key handled ordered synchronization by version & a GSI handled direct lookup by record ID. Two query patterns. Two native DynamoDB mechanisms. Done. I then asked whether another storage technology would fit the architecture better. Instead of evaluating the architecture, the model began redesigning it. At the end of its answer, it suggested replacing the GSI with a second table that mapped every record ID to its current version. The proposal worked. That was the problem. It duplicated a job DynamoDB already handled, introduced another table to maintain, and created another piece of state that had to remain correct. Nothing in my requirements justified it. When I challenged the suggestion, the model quickly agreed: the GSI was simpler and better suited to the system. The model had not lacked technical knowledge. It had lost the objective. I asked: Is there a better tool for this architecture? It answered: How could I redesign this architecture? That distinction is easy to miss in a chat. In a real codebase, it becomes extra tables, migrations, abstractions, failure modes, and maintenance. AI-generated plans still need to be read as critically as AI-generated code.

@suryanox7 The line moved from features to guarantees. Postgres will store your JSON but won’t promise it scales past one box. DynamoDB will give you a transaction but won’t promise it’s cheap or crosses partitions freely. Everything’s possible now, just priced differently.

If SQL database can store documents, and NoSQL database support transactions, where’s the line today? 🤔

@Lomehn That one’s always a name mismatch, a wrong region, or wrong creds, and it takes way longer to find than it should. We catalogued it here: dynotable.com/dynamodb-error…

Just spent hours trying to debug an error only to find out the cause was a simple name mismatch between my dynamoDB table name and the one in my lambda py file. I’m not okay. 🙂

@broisnees @solopribuilds Took a different approach with very specialized DynamoDB GUI dynotable.com

@solopribuilds database client for agent and humans : stroke.click

Saturday should be for promotions Building something? Drop the link 👇

@kelvinbuildss Any NP problem would be nice 😂

What problem would you like to see AI solve?

Before you build it, the modeling half already exists: dynotable.com/tools/dynamodb… You type entities and access patterns, it hands back PK/SK templates, adds a GSI only where the base table can’t serve a pattern, and spits out CreateTable JSON. It’s browser not CLI, so if you want the dynamodb create-table step wired in, that’s the part worth building.

Alright, I’m gonna just build it myself. A cli tool where you just model your DynamoDB tables and access patterns and the tool does the rest, determining pks, sks, and GSIs for you and building the table for you based on your model. No more frustration. #buildinpublic #dynamodb

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

Interviewed a candidate who used DynamoDB in their system design. Unprompted, they mentioned learning everything from @alexbdebrie's The DynamoDB Book. A new career goal for me is to have my work referenced in interviews.

@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.

The fix: the suite now runs in every commercial region and scores each engine against the one it matches best. Eight engines, tracked run over run: paritysuite.org #dynamodb #aws

My own DynamoDB emulator started failing a conformance test it used to pass. I hadn't touched the code. AWS changed a validation rule in eu-west-2, then reverted it weeks later - my suite trusted that one region as ground truth. martinhicks.dev/articles/you-c…

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

Typo alert: Some customers saw quadrillion-dollar AWS billing estimates today. Slight miscalculation on our end (very slight 😅). We're fixing it now. No action needed on your end. Sorry for the confusion. Real question: what will you do with those trillions instead?

@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

People saying "it's just a matter of time" - where will the training data come from? Coding LLMs have benefitted from billions of lines of open source repos with comments, discussions, commit histories; all useful free data that points towards what is definably "good code". There is no such resource for "good design" to train on. Even when good design hits git repos in the form of UIs / landing pages etc, it has gone through countless offline revisions that LLMs don't have access to. Good design rules are scattered around in books, company design systems / guidelines, private email threads, meeting notes, or simply kept in designers' heads left verbally unarticulated. You simply won't see the same level of acceleration in design capability as you did for coding, with AI.

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…

#CloudComputing I have a customer who wants a multi-cloud architecture for flexibility and redundancy (in case one goes down). But the cost you pay for that insurance is high, and likely to fail for multiple reasons: (via Ahmad Kanj, dev.to/aws-builders/d…)

@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…

@shar1z Sounds like a typical Wednesday of using DynamoDB 🙈🙈🙈

I honestly can't stop laughing from this. This is the funniest bug ever. This just about sums up exactly how I imagine every engineer is reacting right now.

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…

Why does DynamoDB (and document dbs in general) have to be so difficult to model? Every tutorial starts with PKs, SKs, and GSIs. I just want to model my data not come up with an entire access architecture before I’ve written a single line of code. #dynamodb #buildinpublic

@Nishanttt05 DynamoDB!

Be honest Which database is worth using in 2026?

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…

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

DynamoDBのGSIのキーって、後から変更できないの今日またハマって確認した。何回目だろうこれ。

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.

Stop using AWS Glue daily exports for your #DynamoDB BI layer. Convert to incremental #CDC streams with DynamoDB Streams + Firehose + Redshift. That batch pipeline has a ticking clock banandre.com/blog/dynamodb-…

@Taniyatweets_ pnpm all day, every day

What's your go to package manager right now?