Why SQL is beating NoSQL, and what this means for the future of data

Re:Why SQL is beating NoSQL, and what this means for the fut... by elvinyung on Tuesday September 26, 2017 @02:42PM (#15341443)

I said open source and mature :)

IMO really the best option for distributed OLTP RDBMS/NewSQL right now is basically either Citus or Vitess, only because they are built on the backs of extremely mature databases. It really feels like all other options are not mature enough (except maybe VoltDB).

[ Parent | on HN ]

Re:Why SQL is beating NoSQL, and what this means for the fut... by jinqueeny on Tuesday September 26, 2017 @06:45PM (#15343270)

Could you please elaborate how you define "mature"?

[ Parent | on HN ]

Re:Why SQL is beating NoSQL, and what this means for the fut... by elvinyung on Wednesday September 27, 2017 @03:13AM (#15345542)

IMO, in descending order of importance to me:

* Dependability. I can be completely certain that standard usage of the database won't lose my data or leave it in a bad state, at the very least.

* Community. There's an active IRC channel (or the like) where I can ask questions. When an error show up, I can Google it and easily find an applicable solution most of the time.

* Performance. Not just with synthetic (i.e. TPC-C, TPC-H, YCSB, etc.) workloads, but proven to have reasonably satisfactory QPS in many/most real production settings.

* Ecosystem. There's a good collection of first-party (and also ideally third-party) tools, constantly being improved. (Mere wire-compatibility with MySQL or Postgres might be good, but probably isn't enough, since 100% wire compatibility seems rare.)

[ Parent | on HN ]

Re:Why SQL is beating NoSQL, and what this means for the fut... by jinqueeny on Wednesday September 27, 2017 @04:26AM (#15345845)

Thanks for sharing！These criteria seems quite practical. You are probably right. Time will tell.

[ Parent | on HN ]