You are here

Top Questions Asked About the NuoDB Distributed Database Architecture

When people first hear about NuoDB, they immediately understand the benefits of our core features. Whether they’re attracted to scale-out performance, continuous availability, geo-distribution capabilities, multi-tenancy, or something else entirely, they want to believe it can perform “as advertised.”

Not surprisingly, however, they are naturally skeptical, and as a solution architect, I’m often asked a number of detailed questions about how it all works. Most of those questions are thoroughly answered in our documentation or tech blog. Here, in one place, is an index of some of the most common questions we get asked, and the answers to some of the most useful information.

One of the other questions we get most often involve managing distributed updates. How can we actually support active-active updates to a distributed database, while claiming ACID compliance? Some of this has been answered in the links above, but beyond the “basics”, this question is further qualified by network problems that prevent transaction control messages from being exchanged (AKA network partitioning).Understanding how everything else works first is critical to understanding network partition management. The way we currently handle this (see “Failure Detection and Network Partition Management in NuoDB”) is innovative and works well for many classes of applications. There’s always room for improvement, though, and we’re currently working toward a solution that will take this a step further by healing partitions after network failure.

Comments

What SQL standard does NuoDB follow? 2016? 2011? ...?

And, of that standard, is it a full implementation? If not, what is missing?

Hi Peter - We have a document page listing our SQL compatibility. However, the page has not been updated to show the new standards and our support for those features. If you have a specific compatibility question, please submit a support request. Thanks!

Add new comment