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

科技回声

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

GitHubTwitter

首页

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

资源链接

HackerNews API原版 HackerNewsNext.js

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

Ask HN: Database migration project – which database?

1 点作者 laxentasken将近 7 年前
Hi! I&#x27;m tasked with migrating a existing db project from a proprietary database to &quot;a better solution&quot; as the current one is becoming quite unstable due to various bugs and the fact that it reached EOL years ago.<p>The workflow is pretty simple: mass update existing records or appending new records once in a while (this will be done in a controlled fashion invoked by someone - no services) -&gt; do some ETL work -&gt; re-build existing tables from source after doing some join magic -&gt; export tables for delivery to customers.<p>Tables have around 10 to 100 million rows and 10 to 300 fields (will probably normalize a bit..) The data is relational and as for now the size is ~400GB which I expect to grow around 3% each time. There wont be much reads as the tables will be exported for further process and the the writes will be in a controlled fashion as stated above.<p>I&#x27;m looking at mysql and postgresql - which one would you choose? Or something else?

2 条评论

davelnewton将近 7 年前
It also depends on how the DB is used: read or write heavy? Is the data relational? How much? How do you need to query the data? Etc.
评论 #17319592 未加载
moviuro将近 7 年前
postgrsql&#x27;s future is pretty safe, whereas MariaDB&#x2F;MySQL was pretty worrying for a while.<p>pgsql is closer to the (SQL) standard and has a rock-solid track record.<p>However, given the size of your project, you might want to test both in &quot;real&quot; conditions, see which ones work correctly. You should perhaps even call for a contractor.