liveBook · Manning

Dual-write mode

Dual-write mode is a pattern in which each logical data update is written to two separate destinations or representations.

How 2 Manning books explain it

Grokking Software Architecture

A dual write is an operation that updates two separate systems, such as a database and a message broker, without a shared atomic commit.

How it is used
Introduces dual writes as a synchronization risk in service migration and event publication, and as a temporary mode in schema evolution.
How deep it goes
Defines cross-system dual writes and walks through partial failures and alternatives, without a full outbox implementation.
Examples
Uses order publication, legacy-to-microservice database synchronization, and a phone-column rename to illustrate dual-write scenarios.
What you can do after
Evaluate dual-write failure risks and distinguish migration alternatives from safeguards for a schema-transition window.

Read how Grokking Software Architecture explains dual-write mode →

ScyllaDB in Action

Dual writing is a migration technique that sends each data update to both the source and destination databases.

How it is used
Keeps an online source database synchronized with a migration destination until application traffic can safely move.
How deep it goes
Explains write ordering, consistency retries, timestamp conflicts, and workload limits, but does not specify a complete implementation.
Examples
Uses an editor’s concurrent article update to demonstrate how a migrator can overwrite newer data.
What you can do after
Apply dual writing to prevent missed updates and configure migration timestamps that avoid overwriting newer data.

Read how ScyllaDB in Action explains dual-write mode →

Also covered in

Related concepts

Questions about dual-write mode

What is dual-write mode?

Dual-write mode is a pattern in which each logical data update is written to two separate destinations or representations.

Which Manning books explain dual-write mode?

Grokking Software Architecture and ScyllaDB in Action.

What is the difference between dual-write mode and CDC?

Dual-write mode is a pattern in which each logical data update is written to two separate destinations or representations. Change data capture is a technique for detecting and recording changes to data in a source system so they can be processed or propagated to other systems.

What is dual-write mode part of?

Dual-write mode is part of parallel change. Parallel change is a migration technique that introduces a compatible replacement alongside an existing structure or interface, transitions use to the replacement, and then removes the old one.

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.