Awesome!

thanks 🙂

Nice project! In JS v3 sdk they don’t seem to have DocumentClient for DynamoDB anymore, but they’ve included the utils to marshall from dynamodb-JSON to “normal” JSON and the other way around. https://docs.aws.amazon.com/AWSJavaScriptSDK/v3/latest/modules/_aws_sdk_util_dynamodb.html

Just quickly skimmed through the code. 🙂 Tomorrow I might have time to actually try it out!

hey, thanks! Looks like that would take some of the manual work out of this kind of stuff that I’m doing, right?

(defn build-dynamo-comment-payload
  [comment-input]
  {:PostId {:S (:post-id comment-input)}
   :CommentId {:S (uuid/v4)}
   :Message {:S (:message comment-input)}
   :Time {:S (.toISOString (js/Date.))}
   :Author {:S (:author comment-input)}
   :RecaptchaScore {:S (str (:score comment-input))}})

Yep, exactly. 🙂

very nice, didn’t know about that

Yeh, it’s pretty well hidden!

yeah there’s definitely a lot in those sdks to dig through

I remember it was PITA to add those type attributes.. then I found out that DocumentClient does that automatically. But now they don’t have DocumentClient in v3 which got me confused but luckily they’ve kept the supporting functions around.

Weird that they don’t mention it in the DynamoDB Client README. :thinking_face: I guess 99% of the SDK users would like to use those functions if they knew they existed

that’s good. we actually have some DynamoDB code that we use at my day job in plain old JS and whoever wrote it definitely did not know about these utils. We have that crazy nested { "Field": { "S": "Value" } } type stuff all over the place lol

I guess it’s all generated (code, docs, references) and these weird things on the side get excluded

yeah i guess that makes sense. I’ve looked into that a little bit (not too deeply), but i think it’s pretty amazing how they basically describe all of their apis for all of their services in some generic way and autogenerate all the stuff that they do

i’m kind of in awe of aws

Personally I like their engineering. They have quite clojurey mindset to not break things.

One thing they don’t know how to do is UI’s 😄

OTOH also GCP and Azure have very crappy UI’s

i really like it too. it’s very “DIY” which was/is pretty painful sometimes, but I appreciate the transparency of everything

agreed on the UIs too haha. i try to do everything i can using infra-as-code but i spend time in the UI when prototyping things. but eh, they serve their purpose for me most of the time

Yep, I usually explore in the UI and when I know what I want I write it in Cloudformation

Which is always a journey 😎

i know what you mean 😆