Spider

E190350

Spider is a distributed storage engine for MariaDB that enables sharding and horizontal partitioning of tables across multiple servers.

All labels observed (1)

Label Occurrences
Spider canonical 1

How this entity was disambiguated

Statements (50)

Predicate Object
instanceOf MariaDB storage engine ⓘ
distributed storage engine ⓘ
sharding engine ⓘ
accesses remote MariaDB servers ⓘ
aimsTo enable transparent sharding ⓘ
improve scalability of MariaDB deployments ⓘ
allows cross-node queries ⓘ
placing partitions on different servers ⓘ
splitting a logical table into multiple physical tables ⓘ
transparent access to remote data ⓘ
canBeCombinedWith Galera-based clustering in some topologies ⓘ
MariaDB replication ⓘ
canBeUsedFor horizontal scaling of OLTP workloads ⓘ
large-scale analytical workloads ⓘ
canUse InnoDB on remote servers ⓘ
MyISAM on remote servers ⓘ
compatibleWith MariaDB partitioning framework ⓘ
configuredBy CREATE TABLE and ALTER TABLE options ⓘ
dependsOn underlying storage engines on remote servers ⓘ
designedFor distributed database environments ⓘ
developedFor MariaDB ⓘ
documentationAvailableAt MariaDB official documentation website ⓘ
enables distribution of table data across multiple servers ⓘ
scaling out MariaDB databases ⓘ
implements storage engine API of MariaDB ⓘ
isIncludedIn some MariaDB server distributions ⓘ
licensedUnder GPL (following MariaDB licensing) ⓘ
mayIntroduce additional network latency ⓘ
requires network connectivity between nodes ⓘ
runsWithin MariaDB server process ⓘ
stores connection information to remote servers in table definition ⓘ
supports XA transactions (in some configurations) ⓘ
asynchronous operations to remote servers ⓘ
data locality optimization ⓘ
federated tables ⓘ
horizontal partitioning ⓘ
mapping of partitions to specific servers ⓘ
online reconfiguration of partitions (with care) ⓘ
parallel query execution across shards ⓘ
partition pruning ⓘ
partitioned tables ⓘ
read/write splitting at partition level ⓘ
remote condition pushdown (in some cases) ⓘ
sharding ⓘ
table-level and partition-level configuration ⓘ
transactions (depending on underlying engines) ⓘ
usedFor geographically distributed data storage ⓘ
multi-tenant database architectures ⓘ
usedIn distributed MariaDB clusters ⓘ
uses table partitions as shards ⓘ

How these facts were elicited

Referenced by (1)

Full triples — surface form annotated when it differs from this entity's canonical label.