MySQL || NoSQL
Which is your prefer and why?

It really depends on the project.

@plusgut , for *big* project?
Example;
1-5 technical admins
Nearly 2k classic users at the same time
Nearly 2m total records on db
Nearly 4k of them need to update on weekdays by one of users
And, sometimes adding new lines

@TilkiBey How complex is the data or in other words is the data good normalizable?

But depending on the specs you said I would tend to use an SQL based Database. Postgre or somethimg like it.

@TilkiBey project like this I assume is going to be up time dependent so I would use something like CockroachDB here.

@plusgut data will be very complex due to changable counts of variables. I will check your sayings. Thanks you
👍

@tankerkiller125 hmm, cockroachdb, i will make some tests. Thank you for giving another opinion

YourSQL || YesSQL

I've chosen MongoDB over SQL in any project you would take SQL instead cause their performance is pretty similar and I prefer to have a database more developer friendly.
All my experiences trying to learn SQL deeply was marked by a big frustration.

If I was going to choose a SQL database I would take Postgresql or Mariadb
Why?
MySQL is Oracle property right now, none is sure what will be its future, furthermore Oracle is very known to throw shit on the software community face all the fucking time.

@codesculptor with so many concurrent database actions, mongodb can have data inconsistency. I wouldn't trust it with such a big project.

Depends, i have used both, but framework that i use supports both with same code..

Difference is that one needs migrations the other does not

@plusgut if you follow their documentation and best practices you will not screw up man.

Mongo 3.4 has all the support . It is fast and even has joins and it's fast , developer friendly and one thing it lacks is transition but our organisation build a wrapper around mongo and they support all the SQL features like transaction and rollback .

@codesculptor there default configuration is in my opinion just there for the benchmarks. But is not usable for production. This is not professional which results in a low trustlevel.

@plusgut you should take a look on StackShare and see a lot of companies that just have a different mindset ;)

@codesculptor but would you say that the default setting is usable for production?

p.s. Using software because other companies are using it, isn't a valid argument in my opinion

Any production thoughts about NewSQL? Someone?

@plusgut it depends on what you are building, in some cases neither any SQL database default configuration will help you out very much.
You should take a look on MongoDB's newest version, there is no silver bullets of course.
Futhermore You can't read two or three blog postings and make it an universal truth. Hack, rebuild, hack again, put something on production... Then you talk.

@codesculptor okay fair enough, I'll do that.

It's brilliant in production . We are using it in production . Please specify the issues that you face in production and when used with node it's butter smooth .

I am curious why devRant chooses Neo4j. Why does it need a graph database? Is document based db not sufficient for devRant?

SQL. Preferably Postgres

But why not RethinkDB

@mikk150 it falls under NoSQL. And then there's also that: https://rethinkdb.com/blog/...

NoSQL varies massively depending on what your requirements are, so the question just doesn't contain a context to which one could reply.

However if by NoSQL you mean somewhere to easily store json objects, as well as the known ones like mongo, Postgres (and even MariaDB 10) supports them. I have postgres in both relational and non-relation cases (even combined) and it's very easy and reliable.

Have also used arangoDB for it's graph inyerface and transactional support.

Also ElasticSearch for full text search and geo search.

So you need to decide what your data is like and what sort of operations will be performed. If you don't know that, you could start of by Postgres as it is general purpose, has a great license and high performce and support for wide varierty of datastructures. When youbsee the need, combine it with other tools or even switch if necessary.

@TilkiBey don't use mysql. It's a terrible rdbms.

But if you need acid compliance om your updates you SHOULD still use a sql rdbms probably Microsoft SQL or postgres. And for the love of God, build the application in a way that lets you migratie database technologies easily.

PostgreSQL because Heroku