We are pleased to announce that with NuoDB v3.3, our leading distributed SQL database is now integrated into Red Hat OpenShift. This enables customers to fully develop, test, deploy and operate applications needing a SQL database fully within OpenShift. OpenShift is Red Hat’s open source container application platform based on the Kubernetes for enterprise application development and deployment.

The NuoDB Community Edition (CE) is a full featured, free to use version of

As a distributed, ACID-compliant database, we get a lot of questions about how NuoDB works, and how it compares to more well-known architectures. In particular, people want to understand how NuoDB compares to a master / master architecture, and (related) how we handle lock management. This post will discuss both. We will also discuss when shared-nothing architecture is viable and when conflicting decisions need to coordinated.

In this blog post, we will discuss the concept of Chairmanship, NuoDB's answer to distributed coordination. We will prove that Chairmanship is both

Originally published by The New Stack .

As the executive in charge of customer success, I have perhaps the most intimate, on-the-ground understanding of how customers use our product and where they struggle. One request we have received time and again has been a better way to access system- and domain-level metrics and data to help optimize the resources and deployment of a NuoDB implementation.

That’s why I’

So far we have examined the status quo, wherein various architectural alternatives of achieving improved elasticity and scalability using existing solutions are offered. But each of these methods has some significant drawbacks: shared-disk requires expensive hardware and software to achieve, shared-nothing requires partitioning the data that may not match the requirements of all applications, and NoSQL eliminates ACID and often, SQL. Clearly an alternative approach is needed – one that does not try to work around the shortcomings of the existing solutions.