Yes these were my biggest problem with this post; they don't spend the time to try and find out bottlenecks and when they finally do instead of investigating the WHY they're thinking about simply switching to yet another which is going to have the same issues if they're not using an optimal data model, etc.
This is unfortunately a very common problem-solving approach. I've seen devs upgrade jQuery because they're getting a 500 error from a PHP app. No relation to the problem - it's just flailing around in hopes something random works.
> NoSQL is a database choice now, a worse choice in my opinion.
If that's legitimately your opinion on that topic then I suggest you expand your knowledge.
NoSQL databases aren't slot in replacement for SQL databases. However, for what they're good at they're REALLY good at it. Namely highly scalable, Document Storage (or "blobs"), and incredibly low latency reads.
Keep in mind that NoSQL doesn't mean schemaless. You can have a schema and be NoSQL, and that is the direction most NoSQL databases are moving into (or have moved into).
> If that's legitimately your opinion on that topic then I suggest you expand your knowledge.
So, If my knowledge were expanded I would think NoSQL is an equally valid option, and not a worse one? I hesitate to do any more expansion because of this panel held in 2014 [0] asking weather we are in a big data bubble, and probably answering "yes", but I wasn't there.
Simple query language is REALLY good too. It has a kind of general usefulness.
> Keep in mind that NoSQL doesn't mean schemaless. You can have a schema and be NoSQL
> So, If my knowledge were expanded I would think NoSQL is an equally valid option, and not a worse one?
For some things NoSQL would be a better option. For most things SQL remains the better option.
> I hesitate to do any more expansion because of this panel held in 2014 [0] asking weather we are in a big data bubble, and probably answering "yes", but I wasn't there.
We were in a dot-com bubble around 97-2000, maybe the internet is a bad idea also?
> Can you also have SQL and be NoSQL?
By definition, no. But some NoSQL databases do support an alternative to SQL with some of SQL's properties (e.g. JSON-like syntax).