3 ms·

I don't think you can just set a line like that. Eventually the programmer might want to consider what to do in the case of data failure. Otherwise, why even wr

by Retra 9y ago

I don't think you can just set a line like that. Eventually the programmer might want to consider what to do in the case of data failure. Otherwise, why even write shared code? The programmer might be wise to write all their software from scratch, affording every consideration where they know best, but they certainly won't want to start there. And this says nothing for teams where people leave and enter over time and persistent experience is ephemeral.

jedberg 9y ago
This is a fair point. Maybe the engineer doesn't think about it, but at least some engineer wrote a library that takes care of it, instead of relying on the database to do it. And even with a consistent system, maybe they are still using a library. But my point was eventually consistent systems, in general, force you to think about these things earlier on. Of course there are exceptions in both directions.