The Ultimate Guide to High Availability with MariaDB

Spider Storage Engine Core Concepts

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

Contents

  1. Spider Common Usage
  2. Spider Storage Engine Federation
  3. Spider Threading Model

A typical spider deployment his a shared-nothing architecture, the system work with any inexpensive hardware, and with a minimum of specific requirements for hardware or software. It consists of a set of computers, with one or more MariaDB processes known as nodes. The nodes that store the data will be designed as backend servers, and can be a MariaDB, MySQL, Oracle server instance using any storage engine available inside the backend.

The Spider proxy nodes stand for instances running at least MariaDB 10 and define per table attachment to the backend nodes. Spider proxy node can be setup to enable the tables to be mirrored to multiple backend nodes.

Spider Common Usage

Spider3 Spider4

Spider Storage Engine Federation

Spider1

Spider Threading Model

Spider2

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.