When it comes to database high availability, how many 9s do you really need? Finding the right mix of reliability and infrastructure complexity is vital to make the best use of your resources. In this blog, we will take a high-level look at three common approaches, spanning from 99.9% to 99.999% uptime.
The MariaDB project is pleased to announce the immediate availability of MariaDB 10.2.7. See the release notes and changelog for details.
MariaDB ColumnStore is a GPLv2 open source columnar database built on MariaDB Server. It is a fork and evolution of the former InfiniDB. It can be deployed in the cloud (optimized for Amazon Web Services) or on a local cluster of Linux servers using either local or networked storage. In this blog post, I will show some examples of analysis of financial time series data using MariaDB ColumnStore.
The MariaDB project is pleased to announce the immediate availability of MariaDB 10.2.7. See the release notes and changelog for details.
Now in the Microsoft Azure Marketplace: MariaDB TX 2.0 with MariaDB Server 10.2, configured in a MariaDB Galera Cluster topology, with MariaDB MaxScale 2.1, and Azure Managed Disks.
The MariaDB project is pleased to announce the immediate availability of MariaDB 10.1.25, MariaDB Connector/J 2.0.3, and MariaDB Connector/J 1.6.2. See the release notes and changelogs for details.
Hyper-V is the native virtualization technology contained within Windows 10 Professional (and Windows Server & Windows 8 Pro). Using Hyper-V to create one or more virtual machines running Linux, it is possible to run and test multiple types of MariaDB ColumnStore deployment on a single Windows machine.
Optimizing your database performance is important, but it often falls by the wayside in the bustle of daily business. This blog reviews three common performance issues, with easy-to-address tuning solutions.
In this second installment of schema sharing with MariaDB MaxScale to combine SchemaRouter and ReadWriteSplit MaxScale routers, we'll go through the details of implementing it in order to shard databases among many pairs of master/slave servers.
Most of the time when you start a database design you don’t imagine how your applications need to scale. Sometimes, you need to shard your databases among some different hosts and then, on each shard you want to split reads and writes between master and slaves. This blog is about MariaDB MaxScale being able to handle different databases across shards, and splitting up reads and writes into each of the shards to achieve the maximum level of horizontal scalability with MariaDB Server.
After reading this blog you will be able to:
Know how MariaDB MaxScale handles shards with SchemaRouter router;
Know how MariaDB MaxScale handles the split of reads and writes with ReadWriteSplit router;
Know how we can combine both mentioned router in order to have an scalable environment.