3 ms·
Dual writing has huge downsides: namely you're now moving consistency into the application, and it's almost guaranteed that the databases won't match in any int
by jtc331 4y ago
Dual writing has huge downsides: namely you're now moving consistency into the application, and it's almost guaranteed that the databases won't match in any interesting application.
- aeorgnoieang 4y agoI'd think using built-in replication (e.g. PostgreSQL 'logical replication') for 'dual writing' should mostly avoid inconsistencies between the two versions of the DB, no?
- jtc331 4y agoYes, though I've only ever seen people use the term "dual writing" to refer to something at a higher-than-DB-level. The way I've done this involves logical replication also: https://news.ycombinator.com/item?id=31087197 https://news.ycombinator.com/item?id=31087197
- strictfp 4y agoPlus that you need to architect this yourself, with all the black magic involved to not mess something up.