Our live webinar on how to build and scale an application with MariaDB on Docker was so well attended that we weren’t able to get to all the audience questions at the end. Here are our answers to the ones we missed during the live session.
Note: Replication Manager is developed and maintained by community members. It can be used with MariaDB Server, but it is not supported with an enterprise subscription (e.g. MariaDB TX).
This is a follow-up blog post that expands on the subject of highly available cluster, discussed in MariaDB MaxScale High Availability: Active-Standby Cluster.
Relational databases store data in rows because a typical SQL query looks for multiple fields within a record. For example, if you ask for name, zip code and email address of all your customers in New York, the result is presented in rows, with each row containing several fields from a single record. Row structures are also well optimized to handle a lot of inserts and updates.
MariaDB’s new analytics engine – MariaDB ColumnStore - has been in the works for some time. What is it and how did it come about? This post outlines our thinking in choosing the engine and features we implemented.
Last week we continued the MariaDB Roadshow in Europe and visited Paris, Brussels and Amsterdam. We have now completed 5 out of 10 events from this tour. The interest in this roadshow is overwhelming - in Amsterdam we even needed to put extra chairs into the room! So far attendees of the roadshow series especially liked topics around MariaDB MaxScale, security features in MariaDB as well as the MariaDB roadmap session. Monty was among the speakers in Helsinki and Amsterdam.
Applications are often built on top of single MySQL-compliant database instance but often there is a need for more performance and/or availability than what one database instance can provide. Adding slaves or replacing standalone database server with full-fledged MySQL-compliant cluster often requires changes to the application.
If you want to avoid downtimes in your business, High Availabilty (HA) is a strong requirement which, by definition, makes it possible to access your data all the time without losing (any) data. In this blog we compare two alternatives: Oracle RAC and MariaDB Galera Cluster.
It's important to understand which Galera version you are running, for proper compatibility of MariaDB with the Galera replication library, and also to check which featureset you have access to. However, Galera version numbering can be difficult to decipher because of its complex scheme.
Version numbering in Galera consists of three different components:
MaxScale, an open-source database-centric router for MySQL and MariaDB makes High Availability possible by hiding the complexity of backends and masking failures. MaxScale itself however is a single application running in a Linux box between the client application and the databases - so how do we make MaxScale High Available? This blog post shows how to quickly setup a Pacemaker/Corosync environment and configure MaxScale as a managed cluster resource. We will guide you step by step on how to enable basic High Availability by setting up three Linux Centos 6.5 servers with MaxScale.
Let's assume you want to start an automatically expanding and shrinking MySQL replication cluster with up-to seven database servers. This blog shows how to setup up and start MaxScale to work with a master and a single slave and, when needed, how it adapts to the changing cluster configurations. While the set up here is simple similar behavior can be applied in bigger and more complex scenarios.