Thread by @QuinnyPig

As threatened last week, let's kick the tires on @dynobase, a pay-for desktop DynamoDB client.

Granted, it's only gotta beat the @awscloud console experience...

I start by downloading it from the internet. As opposed to what, exactly?

I add a profile and it auto-detects which regions have DynamoDB resources within it. Don't let it fool you; that takes a lot of queries.

Also don't let the "test" in "clicktracker-test" fool you. It's very much production because of course it is.

This is a clue as to my awesome software development practices.

Okay here we see what I have so far for next week's newsletters. 397 DynamoDB RCUs to query that seems like a lot... because it defaulted to "scan" instead of "query." Seems like a spendy default to me...

The fact that it autogenerates the code and copies it to my clipboard for whatever I'm looking at is kinda great. So boto3 / Python would be:

Which given how wordy DynamoDB is... yeah. I don't ever want to hear from anyone on that team that *I* talk too much.

This is snazzy.

Since this data basically never changes, I'd like it if it could "cache" the entire table locally so AWS doesn't earn valuable pennies from me reloading the view.

It's also not clear what "Streams" does as an option but I'm curious to find out.

Oh right I should explain myself.

To start, these three tables are all listed on this diagram. Could they all be one table? I dunno, could you mind your manners?

https://twitter.com/Grundlefleck/status/1440348183310209037?s=20

As to the schema, a single click in Dynobase shows me this. The "issue" is the partition key, the sort key is the "url". Both are strings because boto3.

Every @lastweekinaws link since late 2017 is in this table. So are most of my blog posts since last year.

The best architectures look like shitposts, don't they?

I assure you everything in that diagram is very real.

https://twitter.com/JellybobUK/status/1440349535083974663?s=20

"Are you really using Route 53 to store the issue number?"

I dunno, why don't you `dig TXT issue.nextweekinaws.com` and tell me?

Oh, right– duh. Sorry, this code was written by The Worst Bastard In Tech: me more than a month ago.

https://twitter.com/williamsross/status/1440350767093747722?s=20

So my take on @dynobase: I suspect it's handier if you do things that are more complicated with tables than I do; I mostly treat DynamoDB as a key value store that isn't Route 53.

Will keep it installed for the next time I go careening into database land...

It's worth noting that downloading the app, installing it, and running it was still less friction than logging into the AWS DynamoDB console.

I wish for an iPad version.