these instantaneous writes to the replica node is an example of strong consistency.
That's just an example of real-time replication, not strong consistency. Strong consistency is that the database returns success to the client when all (or a quorum of) replicas have been written.
You can have very fast replication and still incur consistency issues. And very fast replication without a consistency guaratnee is a big problem. Sure, maybe it's fast enough for your workload, but sometimes the writes fail. If that happens, but the first write didn't, you have data corruption.
One of the root problems were untouched here. OP was added to a project running an nosql db in eventual consistency mode, during onboarding no one told him. No one was able to see the landmine in their face during code review. If you go eventual consistency the whole culture changes around it, it's the first directive you think about. At all times.
Hmm that's fair. Tbh I'd say when this happened - 1. I was not a good enough engineer to understand the implications and 2. I'm pretty sure that other than a couple of senior engineers not many people knew.
Gamplato@reddit
Just FYI:
That's just an example of real-time replication, not strong consistency. Strong consistency is that the database returns success to the client when all (or a quorum of) replicas have been written.
You can have very fast replication and still incur consistency issues. And very fast replication without a consistency guaratnee is a big problem. Sure, maybe it's fast enough for your workload, but sometimes the writes fail. If that happens, but the first write didn't, you have data corruption.
TwentyCharactersShor@reddit
Has the bar fallen so low?
Understand the architecture you're playing with.
Zomgnerfenigma@reddit
One of the root problems were untouched here. OP was added to a project running an nosql db in eventual consistency mode, during onboarding no one told him. No one was able to see the landmine in their face during code review. If you go eventual consistency the whole culture changes around it, it's the first directive you think about. At all times.
smit2k14@reddit (OP)
Hmm that's fair. Tbh I'd say when this happened - 1. I was not a good enough engineer to understand the implications and 2. I'm pretty sure that other than a couple of senior engineers not many people knew.