How it Works
If you’ve gotten this far, you’ve seen us make some big claims, and you want to know how — and whether — we can back them up.
Read on to find out more about NuoDB’s Durable Distributed Cache (DDC) Architecture and how it supports a geo-distributed, transactional database that scales elastically on demand.
How We’re Different
Whether you’re developing a new application or upgrading an existing one, you’ve likely experienced how database limitations impact development.
The inability of traditional monolithic databases to meet today’s elastic scalability and availability requirements has led to imperfect and partial solutions such as sharding, database replication, and non-transactional NoSQL stores.
NuoDB represents a different approach. Rather than bending existing architectures to a breaking point or underestimating the value and ubiquity of standard, transactional SQL, NuoDB takes the design principles of a distributed system – a coordinated, message-based network of nodes that can tolerate both failure and change – and combines it with the ACID semantics required of a true SQL system.
Durable Distributed Cache
Under the hood of NuoDB lies a concept we call Durable Distributed Cache (DDC). Let’s break that down.
Ultimately, NuoDB’s Durable Distributed Cache is a memory-centric, peer-to-peer system that ensures ACID compliance, resiliency, and scale-out performance across multiple data centers.
This architecture empowers administrators to make and change operational decisions without affecting application logic.