TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Ask HN: Who is using AWS Aurora in production?

6 点作者 netshade大约 9 年前
AWS Aurora has been in general release since July 2015. I&#x27;ve been considering using it for a larger project, but casual reading of the AWS forums ( https:&#x2F;&#x2F;forums.aws.amazon.com&#x2F;search.jspa?objID=f60&amp;q=Aurora&amp;x=0&amp;y=0 ) suggest its performance gains are not universal, has high replication lag and is generally unstable for some.<p>I was initially very excited for it based on their AWS deep dive talks, but the AWS forums have tempered my enthusiasm somewhat. Is there anyone here using it in production that would care to share stories of its use, and any pitfalls they encountered?

2 条评论

jds86930大约 9 年前
We use it in production on some pretty heavy platforms, and we&#x27;re considering moving more platforms onto it.<p>My feedback:<p>* Read&#x2F;write performance is as good or better than you will get on any other MySQL platform, and much better in some cases. We didn&#x27;t really choose Aurora explicitly for it&#x27;s performance gains so YMMV.<p>* Replicas had some serious lag issues on earlier versions of Aurora, but they&#x27;ve completely disappeared for us after the 1.6 patch (released in March 2016).<p>* Peace of mind with replicas is worth a lot. They shouldn&#x27;t ever fall out of sync with the writer node, they lag less than traditional async MySQL replication (as of the 1.6 patch), &amp; failover to them is pretty fast&#x2F;easy.<p>* We had mild stability issues for a while, but those have also largely gone with the 1.6 patch.<p>* Pitfall: if you&#x27;re heavy on big temp-tables for on replica nodes, then you might not get great performance on creation &amp; reads from those temp-tables.<p>* Protip: if you&#x27;re in a Java-based stack, use the MariaDB JDBC driver (in Aurora mode). This eases farming out queries to replicas, and makes failover a lot easier&#x2F;quicker.<p>I&#x27;d also say that Aurora isn&#x27;t a fix for a bad data model and&#x2F;or lack of indexes. We&#x27;ve noticed that CPU% is pretty comparible to any other flavor of MySQL for heavy&#x2F;complex query workloads.<p>I recently spoke about Aurora at an AWS Summit. Video here: <a href="https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=qvMKKDbzaxo" rel="nofollow">https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=qvMKKDbzaxo</a>
评论 #11702311 未加载
thethimble大约 9 年前
We&#x27;re using Aurora in production at GoGuardian. We&#x27;ve got several instances performing 100s of millions of writes per day. We&#x27;ve found the performance gains to be quite staggering - not only higher throughput for reads and writes but much lower and much more consistent latency for all queries. We&#x27;ve had some issues with stability, but the performance wins are overwhelmingly worth it.<p>Edit: I gave a talk about our use of Aurora at an LA AWS meet up. I&#x27;m not sure if there&#x27;s a video floating around but here are the slides: <a href="https:&#x2F;&#x2F;docs.google.com&#x2F;presentation&#x2F;d&#x2F;10AZU-knzthpS4i21B10SO7MGsNxiR3GSibGK4FnRCWM&#x2F;edit?usp=sharing" rel="nofollow">https:&#x2F;&#x2F;docs.google.com&#x2F;presentation&#x2F;d&#x2F;10AZU-knzthpS4i21B10S...</a>
评论 #11702313 未加载