Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

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.


I'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?


Yes, 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


Plus that you need to architect this yourself, with all the black magic involved to not mess something up.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: