✍️5 Things I Learned from The DynamoDB Book
Alright folks, I had the chance to review @alexbdebrie's incredible new book on @dynamodb
swyx.io/writing/dynamo…
Time for one of my Epic Book Reviews™!
Thread form below:👇
Alright folks, I had the chance to review @alexbdebrie's incredible new book on @dynamodb
swyx.io/writing/dynamo…
Time for one of my Epic Book Reviews™!
Thread form below:👇
You can roughly group the book in 4 parts.
Chapters 1-6 (~120 pages) - Explaining DynamoDB Concepts, APIs, and Expressions
it's dynamodbguide.com expanded!
Chapters 7-9 (~50 pages): Advice for DynamoDB Data Modeling/Implementation
Preview:
Chapters 1-6 (~120 pages) - Explaining DynamoDB Concepts, APIs, and Expressions
it's dynamodbguide.com expanded!
Chapters 7-9 (~50 pages): Advice for DynamoDB Data Modeling/Implementation
Preview:
A lesser book would stop here - mostly explaining factual statements in a more accessible way than the official docs, and then ending with some advice.
That's fine and a fair deal for many technical books.
But this book *keeps going*.
That's fine and a fair deal for many technical books.
But this book *keeps going*.
Chapters 10-16 (~90 pages): Strategies for one-to-many, many-to-many, filtering, sorting, migrations, and others
Example: alexdebrie.com/posts/dynamodb…
Chapters 17-22 (~150 pages): 5 increasingly complex Data Modeling Examples - modeling @GitHub with DynamoDB!?? 🤯
Example: alexdebrie.com/posts/dynamodb…
Chapters 17-22 (~150 pages): 5 increasingly complex Data Modeling Examples - modeling @GitHub with DynamoDB!?? 🤯
In other words - The MAJORITY of the book is a strategy manual and applications for real world examples.
This turns the book from a read-once-and-discard deal into a reusable reference tome you will consult for the entirety of your DynamoDB usage.
This turns the book from a read-once-and-discard deal into a reusable reference tome you will consult for the entirety of your DynamoDB usage.
5 Things I Learned pt 1
Why Generic PK and SK names - because Single Table Design, yes, but also because DDB is a low level, high performance tool:
swyx.io/writing/dynamo…
Why Generic PK and SK names - because Single Table Design, yes, but also because DDB is a low level, high performance tool:
swyx.io/writing/dynamo…
5 Things I Learned pt 2
Q: Why Global Secondary Indexes?
A: Flexibility > Strong Consistency.
swyx.io/writing/dynamo…
Q: Why Global Secondary Indexes?
A: Flexibility > Strong Consistency.
swyx.io/writing/dynamo…
5 Things I Learned pt 3:
KSUIDs for Unique, Sortable IDs. They seem like a great idea useful beyond DynamoDB!
swyx.io/writing/dynamo…
KSUIDs for Unique, Sortable IDs. They seem like a great idea useful beyond DynamoDB!
swyx.io/writing/dynamo…
5 Things I Learned pt 4:
Sparse Indexes for Filtering. A favorite trick of Alex's
swyx.io/writing/dynamo…
Sparse Indexes for Filtering. A favorite trick of Alex's
swyx.io/writing/dynamo…
5 Things I Learned pt 5:
Normalization is OK! It's the only way to do many-to-many, social network style relationships.
swyx.io/writing/dynamo…
Normalization is OK! It's the only way to do many-to-many, social network style relationships.
swyx.io/writing/dynamo…
Final, personal note - I think this is the first book I've extensively previewed that successfully made it to the finish line - which got me this ack alongside these awesome people!
I don't belong among the pantheon of AWS Heroes yet but this small honor is deeply flattering
I don't belong among the pantheon of AWS Heroes yet but this small honor is deeply flattering
