Creating Tables with DynamoDB Toolbox
I'm playing around with DynamoDB Toolbox, and one thing that wasn't clear in my mind was how do I actually create a table using the definitions I made using Toolbox.
Quick GitHub issues search lead me to this issue:
where Simlu was asking the same question, and the answer was "Do It Yourself".
I dread code duplication especially around things like table definitions - it's trivial to have all your tests pass, but in the end, the app fails in production because you have a mismatch between two definitions of the same thing.
I've made a little example repo and a helper. For now, feel free to just copy and paste it.
A helper like this might get into the dynamodb-toolbox itself, so I didn't create a package for it yet. But if jeremydaly decides this code should live in a package, I will do that.
import type { DynamoDB } from "aws-sdk";
type DynamoDBTypes = "string" | "number" | "binary";
type ToolboxData = {
partitionKey: string;
sortKey?: string;
attributes: {
[key: string]: DynamoDBTypes;
};
name: string;
};
function getAttributes(tableDefinition: DynamoDB.CreateTableInput) {
const typesMap: { [key: string]: DynamoDBTypes } = {
S: "string",
N: "number",
B: "binary",
};
return tableDefinition.AttributeDefinitions.reduce((previous, current) => {
return {
...previous,
[current.AttributeName]: typesMap[current.AttributeType],
};
}, {});
}
function getPartitionKey(tableDefinition: DynamoDB.CreateTableInput) {
return tableDefinition.KeySchema.find((k) => {
return k.KeyType.toUpperCase() === "HASH";
}).AttributeName;
}
function getSortKey(tableDefinition: DynamoDB.CreateTableInput) {
const rangeAttribute = tableDefinition.KeySchema.find((k) => {
return k.KeyType.toUpperCase() === "RANGE";
});
return rangeAttribute ? rangeAttribute.AttributeName : undefined;
}
export const dynamoSdkToToolbox = (
tableDefinition: DynamoDB.CreateTableInput
): ToolboxData => ({
partitionKey: getPartitionKey(tableDefinition),
attributes: getAttributes(tableDefinition),
sortKey: getSortKey(tableDefinition),
name: tableDefinition.TableName,
});
(there are tests for it in the example repo)
This is how to use it. Assuming you have a table definition using AWS SDK format:
pass it to the dynamoSdkToToolbox helper:
This will set things like attributes, partitionKey, sortKey, and name for you - making sure they are and stay in sync.
Using the same table definition you can create a table (although you would probably use cloud formation or CDK for that, that's a topic for a separate article, but you might want to use a helper like this to transform the SDK definition to CDK https://gist.github.com/lgandecki/e7806462ce7c3d0d47ce65d44c5aa43d )
Feel free to play around with the code:
Let me know if you have any questions or thoughts in the comments below.
Let us help you on your journey to Quality Faster
We at Xolvio specialize in helping our clients get more for less. We can get you to the holy grail of continuous deployment where every commit can go to production — and yes, even for large enterprises.
Feel free to schedule a call or send us a message below to see how we can help.
Add types to your AWS lambda handler
Lambdas handlers can be invoked with many different, but always complex, event arguments. Add to that the context, callback, matching return type and you basically start listing all the different ways that your function can fail in production.
How to expose a local service to the internet
From time to time you might need to expose your locally running service to the external world - for example you might want to test a webhook that calls your service. To speed up the test/development feedback loop it would be great to be able to point that webhook to your local machine.
For loops in JavaScript (vs _.times)
From time to time I still see a for loop in JavaScript codebases. Linters are frequently angry about them. Let's see how we can replace them.