The Ultimate Guide to High Availability with MariaDB

ColumnStore Architectural Overview

You are viewing an old version of this article. View the current version here.

Contents

  1. User Module
  2. Performance Module
  3. Storage

MariaDB ColumnStore is a columnar storage engine designed for distributed massively parallel processing (MPP), such as for big data analysis. Deployments are composed of several MariaDB servers, operating as modules, working together to provide linear scalability and exceptional performance with real-time response to analytical queries. These modules include User, Performance and Storage.

columnstore-arch-diagram

User Module

User Modules are MariaDB Server instances configured to operate as a front-ends to ColumnStore.

The server runs a number of additional processes to handle concurrency scaling. When a client queries the server, the storage engine passes the query to one of these processes, which then break down the SQL request and distributed the various parts to one or more Performance Modules to process the query and read from storage. The User module then collects the query results and assembles them into the result-set to return to the client.

For more information, see the ColumnStore User Module.

Performance Module

Performance Modules are responsible for storing, retrieving and managing data, processing block requests for query operations, and for passing it back to the User module or modules to finalize the query requests.

The module selects data from disk and caches it in a shared-nothing buffer that is part of the server on which it runs. You can configure as many Performance modules as you want. Each additional module increases the size of the cache of the overall database as well as the amount of processing power available to you.

For more information, see ColumnStore Performance Module.

Storage

MariaDB ColumnStore is extremely flexible with the storage system. When running on premise, you can use either local storage (that is, the Performance Modules), or shared storage, (for instance, SAN), to store data. With Amazon EC2 environments, you can use ephemeral or Elastic Block Store (EBS) volumes. In situations where data redundancy is required for shared-nothing deployments, you can integrate it with GlusterFS.

For more information, see Storage Architecture.

Comments

Comments loading...
Content reproduced on this site is the property of its respective owners, and this content is not reviewed in advance by MariaDB. The views, information and opinions expressed by this content do not necessarily represent those of MariaDB or any other party.