|
|
|
|
|
|
by mighty_warrior
3423 days ago
|
|
|
They maintained a replication process across both tables as they updated the read processes before updating the write process. Say for whatever reason their offline replication process broke for 2 hours. For those 2 hours of downtime that replication is broken, the system is reading from a table that is not in sync with the table that is receiving writes. At that point you are displaying incorrect subscription data to your customers. |
|
|
From the article I got the impression that both tables were being written to in the same database transaction, so this is not a possible failure scenario at all.