Galera Cluster for MySQL is a 100% synchronized cluster in regards to data modification operations (DML). It is ensured by the optimistic locking model and ability to rollback a transaction, which cannot be applied on all nodes. However, schema changes (DDL operations) are not transactional in MySQL, which adds complexity when you need to perform an upgrade or change schema of the database.
Changes made by DDL may affect results of the queries. Therefore all modifications must replicate on all nodes prior next data access. For operations which run momentarily it can be easily achieved, but schema changes may take hours to apply.
Galera R&D team is currently finalizing new features targeted for the next MariaDB 10.5 release. This presentation is a high level overview of the most prominent Galera clustering features under work, such as:
* Non Blocking DDL – for less turbulence of schema upgrades in a cluster
* Cluster Error Voting – for immediate recovery of node failures
* XA transaction Support – for executing XA transactions in a multi-master cluster
* GTID consistency – for consistent GTIDs in hybrid cluster / replication topologies
* Black Box – cluster hardening through more detailed diagnostics
Application-time periods is another feature of SQL-2011. It’s main purpose is to introduce a per-table PERIOD entity, which generally is a pair of temporal fields: [period start, period end), and to set up a new set of syntax and constraints.
Note: the standard forbids these fields to be of type TIME, and to have more than one period per table.
The eminent part of application-time periods is a UNIQUE semantic extension — it adds a possibility to specify a period there, with adding WITHOUT OVERLAPS after it.
MySQL 8.0 has introduced roles, a feature that was present since MariaDB 10.0. There are quite a number of differences between the two databases.
During the MariaDB day Vicențiu will present a comparison between them and see how roles are useful for your application and what are the key differences to consider when working with both databases.
For a large Open Source project to survive, it needs the right testing infrastructure in place. Because of this, the MariaDB Foundation made the whole build system a community shared resource. In this talk we will show how we have accomplished this and how the community can benefit.
MariaDB has an Open Source engine called ColumnStore which provides columnar storage capabilities. During the MariaDB Day Andrew Hutchings (a.k.a. LinuxJedi) will hold a talk explaining what columnar storage is, how it works and the advantages / disadvantages of it. He will also talk about how you can use it to help with things such as your analytical workloads alongside your traditional OLTP workloads.
eBPF on Linux 4.9+ is probably the best way to study performance problems. Basic usage of ftrace interface, bcc tools and bpftrace, as well as main bpftrace features and commands are presented. Several typical use cases (including adding dynamic probes to MariaDB servers, working with stack traces and creating Flame Graphs) are discussed.
As the first MariaDB Day is approaching we begin introducing our speakers. Dmitry Dain will talk about Enabling post-compromise protection for stored data with Virgil PureKit security framework and MariaDB database.
If you’re collecting personal data, you’re responsible for protecting it. And in this day and age, the question of when a database will be compromised is not a matter of “if” but “when.” So how can developers protect data within their systems without hiring expensive consultants or outsourced firms?
In this session, Dmitry Dain presents the Virgil PureKit security toolkit which protects passwords and data from being decrypted even if the database itself is compromised.