All of NoSQL is because of this
maxdemarzi.com
All of NoSQL is because of this
1–10 of 19 posts
Re: All of NoSQL is because of this
#2It 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.
Re: All of NoSQL is because of this
#3What? No. NoSQLs don't help with joins, as they don't have them at all. Meaning every "join-like" has to be client side and entails transmitting stuff to the client, which is even worse than temporary tables.
There are multiple reasons to use NoSQL and non of them is this one.
Having said that - cool, I like relational databases and love my multi-joins going faster.
Re: All of NoSQL is because of this
#4I don't really think this is the main reason people use NoSQL.
Re: All of NoSQL is because of this
#5What? No. NoSQLs don't help with joins, as they don't have them at all . Meaning every "join-like" has to be client side and entails transmitting stuff to the client, which is even worse than temporary tables. There are multiple reasons to use NoSQL and non of them is this one. Having said that - cool, I like relational databases and love my multi-joins going faster.
They don't have joins at all because of how expensive binary joins are to do. NoSQL pre-joins relations (graphs dbs), pre-joins foreign keys (document dbs) , pre-joins everything (queries) (wide column dbs). Saying "all" is a bit of a hyperbole but it gets to the point of the matter.
Re: All of NoSQL is because of this
#6The reason NoSQL exists is that many programmers want a persistent hash table with the guarantees (and man-hour investment) of a database.
(Excluding graph database use-cases, of course.)
Re: All of NoSQL is because of this
#7The reason NoSQL exists is that many programmers want a persistent hash table with the guarantees (and man-hour investment) of a database. (Excluding graph database use-cases, of course.)
At a lot of startups - at least a few years ago - it seemed more like people just not understanding databases at all and wanting to try something new.
I guess since NoSQL isn't new anymore, maybe the database choice at startups is sensible again - as they try something new in another area?
Re: All of NoSQL is because of this
#8All? Seems a stretch...
Re: All of NoSQL is because of this
#9I 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.
Re: All of NoSQL is because of this
#10The reason NoSQL exists is that many programmers want a persistent hash table with the guarantees (and man-hour investment) of a database. (Excluding graph database use-cases, of course.)
At a lot of startups - at least a few years ago - it seemed more like people just not understanding databases at all and wanting to try something new. I guess since NoSQL isn't new anymore, maybe the database choice at startups is sensible again - as they try something new in another area?
To be fair, whether or not you understand SQL, it does integrate spectacularly poorly with most programming languages. Sure you can use ORM, but a massive cost of capability and performance.
Database rows simply aren't objects. You have to squint so hard you risk retinal detachment before the two are even a little bit the same.
Other database paradigms exist, and have existed for a long time. File systems spring to mind. The Windows registry is another.
A case can at least be constructed for using something other than a relational database if all you want is to persist objects in a consistent manner.