First of all, let me clarify and state that consistency in RDBMS is different from consistency in distributed systems. A DBMS (single system) applies consistency to transactional consistency, where, as in distributed systems, consistency means that the presentation from anywhere in the system (reading from any node) is consistent. Thus, a single RDMBS node cannot be considered in relation to the CAP theorem. It's like comparing an apple to an orange.
DBMS with master-slave can be compared with distributed systems. Here, RDBMS can be configured on CA / CP or AP. For example, MySQL provides a way to configure the system so that if a quorum is lost (there is not enough secondary data available to replicate the commit log), the cluster is unavailable (CP system). MySQL also provides a configuration that allows the cluster to work as long as a wizard (CA system) is available with the possibility of data loss. SQL Server AlwaysOn is an AP system because commit log replication is asynchronous (even in synchronization replicas).
Thus, RDBMS can be any of a CA, CP, or AP in a distributed world.
Average joe
source share