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

科技回声

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

GitHubTwitter

首页

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

资源链接

HackerNews API原版 HackerNewsNext.js

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

All of NoSQL is because of this

16 点作者 maxdemarzi大约 2 年前

9 条评论

simonw大约 2 年前
My personal theory is that NoSQL happened because most people found relational database schema changes far too difficult.<p>I&#x27;ve been protected from this by the Django migrations system for over a decade at this point (that landed in Sep 2014, but predecessor South was usable for quite a few years before that point).<p>But if you don&#x27;t have a good migrations system in place, changing the schema of your relational database (and keeping those changes synced across development machines, staging, production etc) is enormously painful - even more so for applications with a lot of production traffic.<p>I&#x27;ve seen many situations where engineers have made sub-par design decisions in order to avoid having to add or modify a column on a large, existing table for a production system.
评论 #34963244 未加载
评论 #34965722 未加载
globalreset大约 2 年前
What? No. NoSQLs don&#x27;t help with joins, as they don&#x27;t have them <i>at all</i>. Meaning every &quot;join-like&quot; has to be client side and entails transmitting stuff to the client, which is even worse than temporary tables.<p>There are multiple reasons to use NoSQL and non of them is this one.<p>Having said that - cool, I like relational databases and love my multi-joins going faster.
评论 #34961037 未加载
评论 #34961888 未加载
评论 #34961889 未加载
评论 #34961649 未加载
twblalock大约 2 年前
The real reason NoSQL took off was ease of onboarding for writing MVP applications really quickly at startups. No need to come up with a detailed and performant table structure in advance -- and that&#x27;s a good thing because your schemas are going to change every week! The languages you use in your stack are probably not typesafe anyway! Just extend the REST API all the way to the database and stick your JSON in it.<p>There are two main reasons it continues to thrive: most developers who entered the industry since ~2010 have not used anything else, and the traditional SQL databases are painful to set up in multi-region cloud topologies without a dedicated DBA team.
maxdemarzi大约 2 年前
It took about 10 years, but worst case optimal joins and multi-way joins in general are finally fixing the Join problem in databases that led to the proliferation of NoSQL systems over the past decade.
acuozzo大约 2 年前
The reason NoSQL exists is that many programmers want a persistent hash table with the guarantees (and man-hour investment) of a database.<p>(Excluding graph database use-cases, of course.)
评论 #34961572 未加载
ergonaught大约 2 年前
I seemingly had a disagreement with a hiring VP last year who asked why I thought NoSQL became so popular. This was not the answer I gave, nor is it the answer he apparently wanted.
below43大约 2 年前
I don&#x27;t really think this is the main reason people use NoSQL.
smilekzs大约 2 年前
Consider changing the title to &quot;Worst case optimal joins&quot;? Original title sounds clickbait-y.
malfist大约 2 年前
All? Seems a stretch...