<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>abalone</author><text>Any experience with using Aurora in place of DynamoDB?&lt;p&gt;A couple years ago there was an interesting tidbit at re:Invent about customers moving from DynamoDB to Aurora to save significant costs.[1] The Aurora team made the point that DynamoDB suffers from hotspots despite your best efforts to evenly distribute keys, so you end up overprovisioning. Whereas with Aurora you just pay for I&amp;#x2F;O. And the scalability is great. Plus you get other nice stuff with Aurora like, you know, traditional SQL multi-operation transactions.&lt;p&gt;It was kind of buried in a preso from the Aurora team and the high-level messaging from Amazon was still, NoSQL is the most scalable thing. Aurora was and is still seemingly positioned against other solutions within the SQL realm. I sort of get it in theory that NoSQL is still &lt;i&gt;theoretically&lt;/i&gt; infinitely scalable whereas Aurora is bounded by 15 read replicas and one write master.. but in practice these days those limits are huge. I think one write master can handle like 100K transactions a second or something.&lt;p&gt;So, I&amp;#x27;m really curious where this has gone in the past couple years if anywhere. Is NoSQL still the best approach?&lt;p&gt;[1] &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;youtu.be&amp;#x2F;60QumD2QsF0?t=1021&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;youtu.be&amp;#x2F;60QumD2QsF0?t=1021&lt;/a&gt;</text><parent_chain></parent_chain></comment><story><title>Amazon DynamoDB Transactions</title><url>https://aws.amazon.com/blogs/aws/new-amazon-dynamodb-transactions/</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>piinbinary</author><text>My wishlist for DynamoDB is now down to:&lt;p&gt;* Fast one-time data import without permanently creating a lot of shards (important if you are restoring from a backup)&lt;p&gt;* Better visibility into what causes throttling (e.g. was it a hot shard? Was it a brief but large burst of traffic?)&lt;p&gt;* Lower p99.9 latency. It occasionally has huge latency spikes.&lt;p&gt;* Indexes of more than 2 columns&lt;p&gt;* A solution for streaming out updates that is better than dynamodb streams</text><parent_chain></parent_chain></comment><story><title>Amazon DynamoDB Transactions</title><url>https://aws.amazon.com/blogs/aws/new-amazon-dynamodb-transactions/</url></story>