NoSQL in MySQL

[davidktw]

 

[peterchan75]

I no s/w expert. But I like Excel Pivot table(something like relational DB) and it can slice and dice database from many angles. I hear AAPL uses nosql. How bad can it be?
In all things created by human, they come in a package(good and bad).

 

[davidktw]

I no s/w expert. But I like Excel Pivot table(something like relational DB) and it can slice and dice database from many angles. I hear AAPL uses nosql. How bad can it be?
In all things created by human, they come in a package(good and bad).

There is nothing wrong with NoSQL, what is wrong is some assume it is a replacement for SQL. That IMHO is truly wrong. Both SQL and NoSQL has their places and their niche.

You understand the strength and weakness of each and you find the one that works best for you. More often than not, I find people jumping to NoSQL and has to settle for the less expressive and sacrificial of ACID when they have not fully explore the RDBMS features and performance offerings yet.

Moreover, why just settle for one? You could have chosen 2 and use them for different purposes. Anything where documents/objects are largely independent of each other and can be isolated on its own service and/or requires extremely large scale design can choose to go with NoSQL.

However a lot of existing schema design that are robust and requires higher integrity which you do not want to make use of complex application tier to ensure correctness can be outsource to a capable RDBMS via SQL. It is very reliable, time tested and also more viable across all programming languages and frameworks. It is also very scalable say with multiple masters, partitioning, sharding, replications and realtime clustering. I must say most projects I have come across do not even come close to testing the limits of a capable RDBMS. Having now even offerings like MySQL and PostgreSQL offers NoSQL within itself, it will be a higher stretch before you need to settle for NoSQL.

For RDBMS, one can have small scale Master/Slave design which a lot of NoSQL doesn’t offer. When I use the “small”, it is not exactly small. Just like “Micro” in “Microservices” isn’t small when you consider the real size of an extremely large scale architecture. For a very long time, Master/Slave design is high available, and scalable if you know how use multiple Master/Slave and multiple replications too. Unfortunately fewer and fewer architects will know about these because they no longer venture into these areas, more and more just knows managed services due to cloud computing offerings.

Sad but true.

 

[davidktw]

 

[davidktw]

 

[davidktw]

 

[xcodes]

bookmarked ...

 

[davidktw]