{"id":2444,"date":"2017-06-16T08:08:00","date_gmt":"2017-06-16T14:08:00","guid":{"rendered":"http:\/\/www.mooreds.com\/wordpress\/?p=2444"},"modified":"2017-06-16T04:29:34","modified_gmt":"2017-06-16T10:29:34","slug":"dynamodb-whats-left-to-manage","status":"publish","type":"post","link":"https:\/\/www.mooreds.com\/wordpress\/archives\/2444","title":{"rendered":"DynamoDb: What&#8217;s left to manage"},"content":{"rendered":"<p>AWS recently announced that DynamoDb will now&nbsp;<a href=\"https:\/\/aws.amazon.com\/about-aws\/whats-new\/2017\/06\/announcing-amazon-dynamodb-auto-scaling\/\">scale read and write capacity automatically<\/a>. &nbsp;While there was already a lot of database administration that DynamoDb took care of (backups, underlying infrastructure provisioning), setting the proper capacities initially, and updating them as your application changed, was a key task that fell to the user. No more.<\/p>\n<p>I posted a link to the news to a discussion channel I participate in, and someone asked: &#8220;what&#8217;s left to manage?&#8221;. Drawing from that discussion, here are a few items remaining:<\/p>\n<ul>\n<li>Appropriate partition keys. &nbsp;Make sure they are&nbsp;<a href=\"http:\/\/docs.aws.amazon.com\/amazondynamodb\/latest\/developerguide\/GuidelinesForTables.html#GuidelinesForTables.UniformWorkload\">spread uniformly<\/a>.<\/li>\n<li>Choosing the right primary key. Since you typically want to avoid table scans and can only query by primary key, making sure you pick the right one is important. &nbsp;(I would also call this &#8220;data model design&#8221;.)<\/li>\n<li>Enforcing data integrity, initially and through time. &nbsp;This is a challenge with every nosql solution.<\/li>\n<li>Creating the&nbsp;<a href=\"http:\/\/docs.aws.amazon.com\/amazondynamodb\/latest\/developerguide\/GSI.html\">appropriate secondary global indices<\/a>&nbsp;for your application.<\/li>\n<li>Securing and controlling access to your data.<\/li>\n<\/ul>\n<p>These are all still important tasks, but DynamoDb is getting easier and easier to use for high performance applications for which nosql is a good fit. &nbsp;(And for which you don&#8217;t mind being tied to AWS.)<\/p>\n","protected":false},"excerpt":{"rendered":"<p>AWS recently announced that DynamoDb will now&nbsp;scale read and write capacity automatically. &nbsp;While there was already a lot of database administration that DynamoDb took care of (backups, underlying infrastructure provisioning), [&hellip;]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[79,13],"tags":[],"class_list":["post-2444","post","type-post","status-publish","format-standard","hentry","category-aws","category-databases"],"_links":{"self":[{"href":"https:\/\/www.mooreds.com\/wordpress\/wp-json\/wp\/v2\/posts\/2444","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.mooreds.com\/wordpress\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.mooreds.com\/wordpress\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.mooreds.com\/wordpress\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.mooreds.com\/wordpress\/wp-json\/wp\/v2\/comments?post=2444"}],"version-history":[{"count":1,"href":"https:\/\/www.mooreds.com\/wordpress\/wp-json\/wp\/v2\/posts\/2444\/revisions"}],"predecessor-version":[{"id":2445,"href":"https:\/\/www.mooreds.com\/wordpress\/wp-json\/wp\/v2\/posts\/2444\/revisions\/2445"}],"wp:attachment":[{"href":"https:\/\/www.mooreds.com\/wordpress\/wp-json\/wp\/v2\/media?parent=2444"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.mooreds.com\/wordpress\/wp-json\/wp\/v2\/categories?post=2444"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.mooreds.com\/wordpress\/wp-json\/wp\/v2\/tags?post=2444"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}