Why NoSql still not popular among most users compare to relational database?

@gthell Because NoSQL has a different use case to relational databases like MySQL and Postgres.

Trying to be agile with RDBMS is hard cause you have to plan out for everything ahead

So basically you’re saying NoSQL should be widely used so you can be lazy with designing your database schemas…? That’s not what NoSQL is for. At all.

It’s also a lie that being “agile” with RDBMS is hard. You don’t need to plan everything up front. Schemas can change just like code.

So basically you’re saying NoSQL should be widely used so you can be lazy with designing your database schemas…? That’s not what NoSQL is for. At all.

I hate to admit this but yes, I find it hard to structure a project that need to deliver 2x time faster than when it suppose to complete.

Through my experience, I find that modifying the RDMBS is much harder on a medium to larger system because one relation change could mean a rewrite to the entire business logic. Everything need to be specs out. Sure small thing like missing column could be added easily but that's not the point I'm referring too.

@gthell Some companies use both, it's mostly a use case.

any small to medium app is better off with NoSql than RDBMS.

No. Most apps have no real use for nosql, and shouldn't be using it in the first place.

It's hugely widespread because a bunch of jackasses promoted it as the best thing since sliced bread, and somehow convinced swarms of (largely javascript) developers to reach for mongo first, rather than ascertain the actual needs of their product/app/whatever and make an informed decision. This often (generally) leads to wildly inefficient data backends that are thrown together on the fly with no care given to what the structure of the data actually ought to be.. not just right this second, but in a week, a month, 5 years.

The complete lack of forethought and foresight that plagues developers lately is endlessly frustrating.

Stop chasing "the shiny" .. think about what you want to do, plan your move(s), and implement with purpose.

Or don't I guess.. but please keep your lazy schema design and cowboy coding at home. There's already far too much of it in the wild.

@jlrdw I would use mongo for storing chat and sql for well plans project. But a team of 2 or 3 like mine doesn't have a luxury to go both.

@willvincent usually, a people without a complaint tend to design the worst database then throw the away their project mid way because. Seen a lot, especially the sql fan boy.

I would use mongo for storing chat

@gthell Why? What is so complicated about conversations and messages that a NoSQL database should be used over a relational database?

usually, a people without a complaint tend to design the worst database then throw the away their project mid way because. Seen a lot, especially the sql fan boy.

What language is this? Incoherent ramblings of a troll, I guess.