Call me maybe: NuoDB
aphyr.com
Call me maybe: NuoDB
1–5 of 5 posts
Re: Call me maybe: NuoDB
#2I think the better argument against the CAP theorem is that while it is true, is it not really that useful. If you have a database with nodes in three data centers, it is much more likely that one of the data centers becomes disconnected (partitioned) from the rest of the internet, rather than that the internet itself is partitioned. In this case, a CP system can still remain available to the internet, it just can't also remain available to the nodes within the disconnected data center.
Re: Call me maybe: NuoDB
#3I think the better argument against the CAP theorem is that while it is true, is it not really that useful. If you have a database with nodes in three data centers, it is much more likely that one of the data centers becomes disconnected (partitioned) from the rest of the internet, rather than that the internet itself is partitioned. In this case, a CP system can still remain available to the internet, it just can't…
Re: Call me maybe: NuoDB
#4I think the better argument against the CAP theorem is that while it is true, is it not really that useful. If you have a database with nodes in three data centers, it is much more likely that one of the data centers becomes disconnected (partitioned) from the rest of the internet, rather than that the internet itself is partitioned. In this case, a CP system can still remain available to the internet, it just can't…
Meanwhile, http://blog.pagerduty.com/2013/04/outage-post-mortem-april-1...
Discussing the CAP theorem is a discussion on what is theoretically possible.
All I am claiming is that it is theoretically possible to make a CP system that, in practice, is highly available. That does not mean one actually exists.
Re: Call me maybe: NuoDB
#5Earlier quoted context omitted.
Meanwhile, http://blog.pagerduty.com/2013/04/outage-post-mortem-april-1...
Discussing the CAP theorem is a discussion on what is theoretically possible. All I am claiming is that it is theoretically possible to make a CP system that, in practice, is highly available. That does not mean one actually exists.
Absolutely agreed; I'm just saying that as the Pagerduty postmortem demonstrates, CP availability becomes trickier as you increase the number of sites--and there are unavoidable minimum latency bounds due to the speed of light. Those bounds may be unacceptably high; this is why Google Spanner chooses instead to enforce strong bounds on clock synchronization.