The Aurora to Amazon Redshift zero-ETL integration atomically replicates transactions to ensure data consistency between the source Aurora database and the target Amazon Redshift cluster. The following are some key points about the atomicity of transactions with this integration:
Only committed transactions in Aurora are replicated to Amazon Redshift. Uncommitted or rolled-back transactions are not applied.
The integration uses a two-phase commit process to atomically apply each transaction to Amazon Redshift. Either all data changes in the transaction are applied, or, if an error occurs none are applied.
Transaction consistency is maintained between the source and target. After replication, the data for a given transaction will be consistent in both Aurora and Amazon Redshift.
Schema changes through DDL or DML are also atomically applied to maintain integrity.
The atomic application of transactions ensures that no partial transactions or inconsistent data states can occur between the databases.