How does GenieDB compare to other DBaaS offerings?
GenieDB uses a proprietary storage engine based that dramatically transforms and enhances the way MySQL functions, enabling continuous availability during any regional outage or network connectivity event. This provides better response time to users anywhere in the world and delivers a simple geo-compliance solution for data protection. Other DBaaS offerings are restricted by the inherent challenges in traditional MySQL replication and distribution. To read more about the inherent problems with standard MySQL, click here to read our whitepaper: Beyond Failover
Is my data multi-tenanted with other users?
No. Each customer runs with a distinct set of nodes with no data storage or communication overlap between customers.
How is data backed up?
Because of GenieDB’s native master-master replication, each node offers a full read/write replica of your data allowing your application to stay up even with entire cloud provider outages. In addition we offer a variety of backup options and schedules including standard MySQL dumps that we can ship to offsite locations.
If I migrate to GenieDB DBaaS, am I locked in to GenieDB?
Never. You can cancel your service at any time. Plus, GenieDB supports standard MySQL dumps, you can easy access to your data and migrate it at any time.
What cloud providers and locations do you support?
GenieDB’s Globally Distributed MySQL as a Service runs on the top cloud platforms, including Amazon EC2, Rackspace, Google Compute Engine, HP Cloud, etc. Your account manager will work with you to ensure we have the cloud infrastructure and geographical location that meets your needs.
How does the pricing work?
Pricing includes GenieDB subscription service charges, the cloud infrastructure fee, such as Amazon EC2, and any server usage charges, similar to other RDS or DBaaS services.
Do I have to pay for the cloud infrastructure charges separately?
When you sign-up for GenieDB, we will track the infrastructure costs from EC2 which are passed through to you and provide you with fully transparent accounting so you know you are not being overcharged.
Is this “NoSQL”?
No! GenieDB is built on MySQL and fully supports SQL and relational models.
How does my application talk to GenieDB?
Using any MySQL client library.
Is GenieDB “MySQL-compatible” or is it really MySQL?
It is MySQL! GenieDB is built as a plugin to MySQL. It can install on stock MySQL 5.1-5.6 on any modern Linux platform.
How do you handle conflict resolution?
GenieDB uses an enhanced Lamport Timestamp to resolve conflicts using last writer priority.
What is Geo-Compliance?
GenieDB Geo-Compliance allows you to define rules for storage and replication of data. This can be used to deliver data localization compliance, enhance application security, and improve replication performance for local clusters.
How do I migrate to GenieDB?
Migration is as simple as a dump of existing MySQL and load into a GenieDB instance.
What limitations do you have over running a single instance of MySQL?
We do have a specific recommendation for autoincs. See the note below on auto increment fields.
How do you handle auto increment fields?
MySQL natively supports increment and offset of auto increment fields in a distributed environment. Each node must be assigned a unique offset to ensure distinct values globally.
How is data communication secured between nodes?
GenieDB uses an AES-256 encrypted channel to communicate between nodes securely. This matches industry best practices for security.
Can you assist in migrating and tuning our application for GenieDB?
We have a team of engineers experienced with migrating from a variety of SQL platforms to MySQL. In addition our experts can review and monitor your application and provide you with a set of key recommendations to further improve your performance and scalability.
Can GenieDB run in the cloud in a vm?
Yes. We have several clients running in virtual machines on a variety of Cloud Providers (Amazon, Google, Rackspace, HP, LayeredTech, Azure, etc) as well internally on VMWare and XenServer.
What about bare metal?
Absolutely! If it runs a modern Linux kernel with MySQL 5.1+ it supports GenieDB.
How are transactions handled?
GenieDB uses an eventually consistent replication model. This means transactions are applied locally and then the individual data elements are distributed. Global transactions are on the roadmap for a future release.
How do you support split brain?
Each node manages a vector clock to determine when a network partition event has occurred and what data requires healing to bring the nodes into a consistent state. This is all done automatically with no user interaction to deliver the best availability of your data possible.