Hear from the co-CTO of Alfa about why they selected NuoDB over traditional and NoSQL databases .
Database Selection: Considering Traditional Relational Databases
The database is foundational to the system. There’s no question. We have to have a solid database underneath the platform, in order for us to provide the product that we do. So, as we move to the cloud, we need a database that will actually move cleanly into the cloud with us. Something that will support the cloud as best as it can. So that was an option. And that remains an option for us. I mean, the traditional databases do work in the cloud. However, they tend to be architected for vertical scaling. Which doesn’t work very well in the cloud environment, where what you want to take advantage of the horizontal scaling capabilities that the cloud provides. So we were looking for a database that was perhaps better suited to the cloud deployment model.
We looked at a number of systems, including various NoSQL options such as Cassandra and MongoDB. But when we looked at those in detail, the main problem is that they don’t support full SQL model. Our system does rely on there being a full SQL database underneath it. And we need to make sure we preserve support for the existing database platforms that we use.
So, moving to something like Cassandra would’ve required a very substantial re-architecting of the system that we didn’t want to do. We don’t want to go down that road. Because we would’ve lost the ability to support the existing databases. So we were looking for a platform that had that cloud-native capability, but also had the full SQL platform.
NuoDB is a full-SQL implementation that works very well both for on-premises deployments and in the cloud on the deployments that -- on things like AWS. It has an active/active deployment model with dynamic scalability and very good uptime characteristics.