<story><title>The DynamoDB Paper</title><url>https://brooker.co.za/blog/2022/07/12/dynamodb.html</url></story><parent_chain></parent_chain><comment><author>mabbo</author><text>Rick Houlihan did a talk a few years ago about designing the data later for an application using dynamodb. The most common reaction I get from people I show it to- most of them Amazon SDEs who operate services that use Dynamodb- is &amp;quot;Holy shit what is this wizardry?!&amp;quot;&lt;p&gt;&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;youtu.be&amp;#x2F;HaEPXoXVf2k&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;youtu.be&amp;#x2F;HaEPXoXVf2k&lt;/a&gt;&lt;p&gt;One of the biggest mistakes people make with dynamo is thinking that it&amp;#x27;s just a relational database with no relations. It&amp;#x27;s not.&lt;p&gt;It&amp;#x27;s an incredible system, but it requires a lot of deep knowledge to get the full benefits, and it requires you, often, to design your data layer very well up-front. I actually don&amp;#x27;t recommend using it for a system that hasn&amp;#x27;t mostly stabilized in design.&lt;p&gt;But when used right, it&amp;#x27;s an incredibly performant beast of a data store.</text></comment>
<story><title>The DynamoDB Paper</title><url>https://brooker.co.za/blog/2022/07/12/dynamodb.html</url></story><parent_chain></parent_chain><comment><author>bistablesulphur</author><text>I&amp;#x27;be been working with DynamoDB daily for a few years now, and whilst I like working with it and the specific scenario it solves for us, I&amp;#x27;d still urge anyone thinking about using it to carefully reconsider whether their problem is truly unique enough that a traditional RDBMS couldn&amp;#x27;t handle it with some tuning. Theycan be unbelievably performant and give so much stuff for free.&lt;p&gt;Designing application specifically for DynamoDB will take _a lot_ of time and effort. I think we could have saved almost a third of our entire development time had we used more of the boring stuff.</text></comment>