This is a quick 2 min overview of Mysql NDB Cluster. The goal is to help you decide within a minute or two, whether this is an appropriate solution for you.
Cluster of in-memory Mysql databases with a shared nothing architecture.
Consists of Mysql nodes and data nodes.
Mysql nodes are Mysql servers that get data from data nodes. Data nodes hold the data using the NDB storage engine. There are also admin nodes.
NDB nodes serve the data from memory. Data is persisted at checkpoints.
Data is partitioned and replicated.
Up to 48 data nodes and 2 replicas for each fragment of data.
ACID compliant.
READ_COMMITTED isolation level.
Sharding of data is done automatically. No involvement of user or application is required.
Data is replicated for high availability. Node failures are handled automatically.
Clients can access data using NDB Api. Both SQL and NOSQL styles are possible.
This is not a good general purpose database. It is suitable for certain specific use cases of telecom and game but not for general OLTP.
Feels like it has too many moving parts to manage.
High performance -- it is serving data from memory.
Summary
Not a general purpose distributed databases. Unless you are in telecom or gaming or know for sure why this meets your use case, don'nt even think about it.
If you are on Mysql and want high availability, try Mysql InnoDb Cluster, which is much easier to understand and use.
References:
Mysql Documentation for NDB cluster
No comments:
Post a Comment