MySQL 8.0 Released With Many Improvements, Faster Performance

[phoronix]

Phoronix: MySQL 8.0 Released With Many Improvements, Faster Performance

It's a busy day in the software and hardware space today as well as a busy week for Oracle with several big releases this week. The latest is the general availability of the long-awaited MySQL 8.0 update...

http://www.phoronix.com/scan.php?pag...L-8.0-Released

[Delgarde]

About json on relational database, it is really useful, you got almost the best of both worlds, at least in my use cases on Postgres

Yep. The JSON part is good for those entities that don't really map well to a fixed table structure in a traditional relation model... but the relational part makes it easier to manage the references between those entities, and the bits that do fit the table model...

[F.Ultra]

For a while it seemed like not much was happening to MySQL and people were migrating away from MySQL to MariaDB which was the "new" MySQL in the same way that LibreOffice became the new OpenOffice.org. Many people feared MySQL would starve under Oracle as happened to many other products under the management of Oracle but it seems that MySQL is alive and kicking.
How does MySQL compare with MariaDB these days?
Are the code bases pretty close or have they diverged significantly?
Which one is the preferred choice?

MariaDB pulls in all the changes Oracle does do MySQL to their codebase while the opposite does not seam to happen (Oracle seams to be really big in NIH) so I would say that MariaDB is the way forward and is also why all the major distributions have switched to MariaDB over MySQL.

[andrei_me]

How these perf numbers compare to MariaDB?

About json on relational database, it is really useful, you got almost the best of both worlds, at least in my use cases on Postgres

[Almindor]

We're closer to a post-NoSQL world, where most people has finished playing with their toys and gone back to work.

This. MongoDB is quite useless for any real world application that grows over your RAM for the working set. It's also useless once you realize you need to do any analytics on the data.

I call it CommentsDB coz it's only good for skript kiddy blog comments sections.

[randomizer]

Is JSON in relational databases truly useful or just a desperate attempt to stay relevant in a post-SQL / NoSQL world?

We're closer to a post-NoSQL world, where most people has finished playing with their toys and gone back to work.

[Delgarde]

JSON is indeed important. But maybe in those cases a real document database such as MongoDB should be used?

The thing is, pure document databases aren't all that useful, because they're *only* good at storing documents. And that suits some domains, sure, but for many others, it's useless, e.g. because they store a lot of relational data that doesn't really fit a document approach. So yes, having a database that supports a hybrid model – mostly relational, but with decent document support – is actually pretty useful.

[uid313]

Back in the day, MySQL lacked some basic features such as foreign keys and triggers. PostgreSQL was years ahead in terms of functionality which gave MySQL a bit of a bad reputation.

Nowadays, MySQL has matured and it is a solid RDBMS. It is Ranked #2 according to DB-Engine and it is by far the most popular open source database available. It is used by some big names out there, definitely not a toy.

Not only that, a lot of other things too. Such as no support for transactions. Then when it supported the transactions the transactions would silently degrade to not being transactions under certain scenarios instead of failing. So even when you wanted to be sure a transaction would go either fully go through or fail, you could never be sure.
I've heard so many bad things about it, how it was behaving incorrectly.

I know MySQL is very popular, because it is an integral part of the LAMP stack and powers so many WordPress sites. But just because it is popular does not mean it is good.
Is it reliable, is it well-behaved these days?

JSON storage is very important. The corporate world is going cloud / micro-services and everyone is working with JSON data. Storing and querying that data makes things so much easier.

JSON is indeed important. But maybe in those cases a real document database such as MongoDB should be used?
I love JSON but is JSON in relational databases just a toy and a desperate attempt to stay relevant or is a real improvement that is really useful?

Don't know if I missed something but I run the queries from the last post by "Pura Vida" on MariaDB (which is MySQL) and saw no deadlocks. Don't say that bugs like these does not exist (every SQL have full bugzillas) but this one I could not reproduce at least not on MariaDB v10.2.14

For a while it seemed like not much was happening to MySQL and people were migrating away from MySQL to MariaDB which was the "new" MySQL in the same way that LibreOffice became the new OpenOffice.org. Many people feared MySQL would starve under Oracle as happened to many other products under the management of Oracle but it seems that MySQL is alive and kicking.
How does MySQL compare with MariaDB these days?
Are the code bases pretty close or have they diverged significantly?
Which one is the preferred choice?

[F.Ultra]

In terms of being a great database to run a website off of, or for a product with relatively few tables and relationships, I agree. If you are talking about using it for enterprise software, leveraging explicit transactions, then no... it sucks. Case in point: https://bugs.mysql.com/bug.php?id=48652


JSON storage is very important. The corporate world is going cloud / micro-services and everyone is working with JSON data. Storing and querying that data makes things so much easier.

Don't know if I missed something but I run the queries from the last post by "Pura Vida" on MariaDB (which is MySQL) and saw no deadlocks. Don't say that bugs like these does not exist (every SQL have full bugzillas) but this one I could not reproduce at least not on MariaDB v10.2.14

[bpetty]

Nowadays, MySQL has matured and it is a solid RDBMS. It is Ranked #2 according to DB-Engine and it is by far the most popular open source database available. It is used by some big names out there, definitely not a toy.

In terms of being a great database to run a website off of, or for a product with relatively few tables and relationships, I agree. If you are talking about using it for enterprise software, leveraging explicit transactions, then no... it sucks. Case in point: https://bugs.mysql.com/bug.php?id=48652

Is JSON in relational databases truly useful or just a desperate attempt to stay relevant in a post-SQL / NoSQL world?

JSON storage is very important. The corporate world is going cloud / micro-services and everyone is working with JSON data. Storing and querying that data makes things so much easier.