MySQL InnoDB Cluster has proven with the first GA release its potential as the native out-of-the-box HA solution for MySQL. With the second GA release, usability, stability and flexibility were greatly improved as described in the previous blog post.
This tutorial aims to show how does a typical InnoDB cluster setup look like and how that setup even became simpler and more effective as before.…
If you are upgrading your server to MySQL 8.0 and observe that your application is experiencing error related caching_sha2_password plugin, it is likely because your clients/connectors does not (yet) support caching_sha2_password plugin. To resolve this issue, you may consider using mysql_native_password as default authentication for MySQL 8.0 server.…
The MySQL Development Team is proud to announce the second GA release of InnoDB cluster!
We listened carefully to the feedback we got from the previous major release (1.0 GA) and the last release candidate (8.0.4 RC) and incorporated many of the suggested changes.…
The MySQL Development Team is proud and happy to announce the General Availability release of InnoDB Cluster 8.0! This is an extremely exciting release of our integrated, native, full stack High Availability (HA) solution for MySQL.
InnoDB Cluster provides an out-of-the-box and easy to use built-in HA and Scaling solution for MySQL by tightly integrating the following GA components:
- MySQL 8.0.11+ Servers with Group Replication, to provide the data replication mechanism within InnoDB clusters, ensuring fault tolerance, automated failover, and elasticity.
In this blog I’ll explain the big wins that come with the MySQL Document Store in the MySQL 8.0 GA.
SQL + NOSQL
= Winning Combination
= Relational + Document Store + Hybrid
= Big Win For Devs
= Big Win for DBAs
= Big Win for Data Analysts
= Big Win for LOB owners
First, let’s start by considering some modern software facts
- Move faster, change rapidly
- Time to market is critical
- Rapid prototyping, iterate fast and frequently
- Relational Models ask for schema up front
- Potentially saving time later
- Less variation, less code for edge cases
- Easy to run in-depth analytics
- Document Models do not ask for a schema
- Saves time up front
- Often adds operational costs in the long term
- Getting Analytics from the data can be way more work
- Most popular NoSQL database use similar data structures to relational databases (B+TREE)
- No inherent scalability advantages
Yet behind on key functionality
- Standing up multiple database technologies adds complexity for operations teams
Customers continually tell us they want to simplify their data infrastructure.…
We proudly announce General Availability of MySQL 8.0. Download now! MySQL 8.0 is an extremely exciting new version of the world’s most popular open source database with improvements across the board. Some key enhancements include:
- SQL Window functions, Common Table Expressions, NOWAIT and SKIP LOCKED, Descending Indexes, Grouping, Regular Expressions, Character Sets, Cost Model, and Histograms.
One of the nice things about MySQL 8.0 is the ability to combine the relational and document models. As a developer, you can choose to work with traditional SQL tables, with schemaless JSON documents, or with both types at the same time.…
In MySQL 8.0 we have replaced the old regular expression library with the ICU regex library. See Martin’s blog on the topic. The main goal is to get full Unicode support for regular expressions, but in addition we get a lot of neat features.…
In MySQL 8.0 we introduce the ICU library to handle our regular expression support. This library is maintained by the Unicode Consortium and is used on a wide variety on platforms. The reason we switch libraries is threefold: security, Unicode support and functionality.…
MySQL 8.0 introduces partial update of JSON values, which is a nice performance improvement for applications that frequently update small portions of large JSON documents. Before, in MySQL 5.7, whenever you made a change to a stored JSON document, the full new JSON document would be written to the database, even if the update just changed a few bytes in the document.…