How NoSQL forced the evolution of a scalable relational database

Re:How NoSQL forced the evolution of a scalable relational d... by threeseed on Friday July 13, 2018 @04:10AM (#17521270)

This is the problem with people that use the term NoSQL.

Do you mean Cassandra (BigTable), MongoDB (Document), Riak (Key/Value), Redis (Mix), Kafka (Log Structured) ? There are dozens of fundamentally different systems many of which are closer to an RDBMS than their NoSQL peers. And many of them have rigid schemas so it definitely isn't that either.

[ Parent | on HN ]

Re:How NoSQL forced the evolution of a scalable relational d... by charlesvdv on Friday July 13, 2018 @07:04AM (#17521886)

You can also add Neo4j (graph) as part of the NoSQL family, right?

[ Parent | on HN ]

Re:How NoSQL forced the evolution of a scalable relational d... by skohan on Friday July 13, 2018 @09:20AM (#17522680)

Yeah in general it seems like NoSQL is used to proxy "MongoDB and other key-value stores."

Graph databases arguably handle relational data better than SQL, and I'd argue they're much nicer to work with.

[ Parent | on HN ]

Re:How NoSQL forced the evolution of a scalable relational d... by eftpotrm on Friday July 13, 2018 @12:39PM (#17524451)

And MS SQL Server now supports graph databases; it doesn't have to be either-or.

[ Parent | on HN ]

Re:How NoSQL forced the evolution of a scalable relational d... by janemanos on Friday July 13, 2018 @05:22AM (#17521547)

Don't forget native multi-model databases like ArangoDB

[ Parent | on HN ]

Re:How NoSQL forced the evolution of a scalable relational d... by fnordsensei on Friday July 13, 2018 @08:22AM (#17522271)

And Datomic.

[ Parent | on HN ]