Today I was able to get pagination working in DynamoDB. Was such a pain getting the page key to serialise/deserialise correctly, but we got there eventually!

#aws #buildinpublic

Took a while to work it out, but I've got my app connected to @localstack DynamoDB now. REST API endpoints are working

#AWS #buildinpublic

Secondly, it looks like I'd have to do this by just creating an additional attribute for this purpose. Is this correct? Or is there a way to tell DynamoDb that my separate EntityId and UserId attributes make up a composite hash key? 2/2

#aws #buildinpublic

I want to create a DynamoDb table that should be queried using the EntityId and UserId. I'm planning to create a composite hash key of EntityId_UserId. Firstly, is this a reasonable idea? The entity would never queried using only the EntityId. 1/2

#aws #buildinpublic

I want to run #AWS DynamoDb locally for development. I see they have a #docker image for this, or I could use @_localstack. Which in your experience is better/easier to use?

#buildinpublic

In an attempt to actually finish a project in the coming year, I'm committing to #buildinpublic. For my first project I'm going to build a link sharing system similar to Linktree.

I'm thinking about building an open source, headless blog system in .NET as a fun side project. What features would you like to see?

#buildinpublic #opensource #DotNet