Dynomite vs Mysos

Overview

Dynomite

Stacks20

Followers56

Votes9

GitHub Stars4.2K

Forks532

Mysos

Stacks2

Followers9

Votes0

Dynomite vs Mysos: What are the differences?

Dynomite: Making Non-Distributed Databases, Distributed. Dynomite is a generic dynamo implementation that can be used with many different key-value pair storage engines. Currently these include Redis and Memcached. Dynomite supports multi-datacenter replication and is designed for high availability; Mysos: MySQL on Mesos. Mysos is an Apache Mesos framework for running MySQL instances. It dramatically simplifies the management of a MySQL cluster.

Dynomite and Mysos belong to "Database Cluster Management" category of the tech stack.

Some of the features offered by Dynomite are:

Replication
Highly available reads
Pluggable Datastores

On the other hand, Mysos provides the following key features:

Efficient hardware utilization through multi-tenancy (in performance-isolated containers)
High reliability through preserving the MySQL state during failure and automatic backing up to/restoring from HDFS
An automated self-service option for bringing up new MySQL clusters

Dynomite and Mysos are both open source tools. It seems that Dynomite with 3.09K GitHub stars and 395 forks on GitHub has more adoption than Mysos with 603 GitHub stars and 69 GitHub forks.

🔥 Trending in Databases on StackShare

PostgreSQL Databases

A powerful, open source object-relational database system

Try it View Docs Alternatives

Try

431

83.9k

Detailed Comparison

Dynomite	Mysos
Dynomite is a generic dynamo implementation that can be used with many different key-value pair storage engines. Currently these include Redis and Memcached. Dynomite supports multi-datacenter replication and is designed for high availability.	Mysos is an Apache Mesos framework for running MySQL instances. It dramatically simplifies the management of a MySQL cluster.
Replication;Highly available reads;Pluggable Datastores;Standard open source Memcached/Redis ASCII protocol support;Scalable I/O event notification server;Peer-to-peer, and linearly scalable;Cold cache warm-up;Asymmetric multi-datacenter replications;Internode communication and Gossip;Functional in AWS and physical datacenter	Efficient hardware utilization through multi-tenancy (in performance-isolated containers);High reliability through preserving the MySQL state during failure and automatic backing up to/restoring from HDFS;An automated self-service option for bringing up new MySQL clusters;High availability through automatic MySQL master failover;An elastic solution that allows users to easily scale up and down a MySQL cluster by changing the number of slave instances
Statistics
GitHub Stars 4.2K	GitHub Stars -
GitHub Forks 532	GitHub Forks -
Stacks 20	Stacks 2
Followers 56	Followers 9
Votes 9	Votes 0
Pros & Cons
Pros 3 Multi datacenters or regions 2 Pluggable APIs (Currently have Redis/Memcached APIs) 2 Low latency high throughput 1 Support many datastores: redis, memcached, rocksdb, etc 1 Scale	No community feedback yet
Integrations
Redis Memcached	MySQL

What are some alternatives to Dynomite, Mysos?

Navicat

Powerful database management & design tool for Win, Mac & Linux. With intuitive GUI, user manages MySQL, MariaDB, SQL Server, SQLite, Oracle & PostgreSQL DB easily.

Galera Cluster

It’s an easy-to-use, high-availability solution, which provides high system up-time, no data loss and scalability for future growth. You can Keep it up and running 24/7. Putting our expertise to use will help you avoid trial and error.

Continuent Tungsten Clustering

It allows teams running business-critical MySQL applications to cost-effectively achieve continuous operations. You may deploy MySQL clusters on-premises, in the cloud, hybrid-cloud or multi-cloud.