PlanetScale 推出分片 Postgres 方案
推荐指数 40.0 NO. 022 · 2026.09.11
发布2026/09/10Score152Comments59
为什么值得看
Neki 是 PlanetScale 基于八年大规模分片 MySQL 运维经验推出的分布式 Postgres 平台预览版，专为突破单机 Postgres 性能上限设计。对正在用 Postgres 支撑高并发业务、且接近硬件瓶颈的 AI 公司和创业团队有直接参考价值。
编辑判断
PlanetScale 从 MySQL 转向 Postgres 分片是个值得注意的信号——这意味着他们判断 Postgres 生态的增长势能已超过 MySQL，且现有方案（如 Citus、 YugabyteDB）在易用性或托管体验上仍有缺口。
Neki 的核心赌注可能是"把 MySQL 分片的运维复杂度藏起来"，而非发明新架构。如果你已经在用 AWS Aurora 或 Cloud SQL 但担心垂直扩展天花板，可以观望 Neki 的 GA 版本是否保留 PlanetScale 标志性的分支式 schema 变更工作流。
分片数据库的选型窗口正在收窄：CockroachDB 偏 NewSQL 重事务，TiDB 生态偏国内，Neki 若能在"无痛分片"上兑现承诺，可能成为海外 SaaS 公司的默认选择。
社区反馈
意见分歧 45 条评论
核心争论：产品技术价值受认可，但营销文案结构混乱导致信息传递失败
Folks, in your launch posts remember to describe what you're launching and what it's for. Ideally in the opening paragraph. - Intro: Explains problem but not what is Neki or what it's for. - Why Neki: Explains alternatives and why they suck but not what is Neki or what it's for. - How does Neki work
The landing page which is linked at the start of the second sentence of this page…? I don’t completely disagree with you, but this is mostly hypertext working as intended, is it not?
Yeah this meta commentary on HN is very confusing for me. The structure of the article is literally - short paragraph saying "we launched neki" - short paragraph saying why neki was needed - paragraphs about what neki is (with a header) That seems like a very reasonable structure for a blog post lik