I've been reading on the promise of an ACID compliant database management system without sacrificing horizontal scaling capabilities.

Where is the catch? Which part of the CAP theorem did they choose to sacrifice? Or did they develop some new database theory solution to be able to cover the whole spectrum?

  • Could you be more specific? Is there something in their architecture whitepaper that seems unclear? – mustaccio Jun 19 '18 at 17:01
  • Which part of the CAP theorem did they choose to sacrifice? This makes no sense - the very theorem states that you cannot have C AND A AND P at the same time (a sacrifice). What you have to ask is Is the system AP or CP? My take on NuoDB is that it is CP - this essentially means that in the event of network failures, the system will choose C over A. This, this and this help. – Vérace Jun 19 '18 at 22:55
  • @Vérace I could have been more clear. But you have gotten my jist. Thanks for the links and you have already answered my question. – IgorR Jun 20 '18 at 9:28
  • I can write this up as an answer if you like - expand obviously. I enjoyed delving a bit more into the topic and it might be nice for posterity... hell, I'll do it anyway - it'll be a learning experience for me - +1 to you for that :-) – Vérace Jun 20 '18 at 10:11
  • @Vérace you gonna convert those comments to an answer or should I? – Michael Green Jul 30 '18 at 5:36

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.