iforgetlogins01

(from the article)

What did NoSQL throw out? Again, that varies from database to database, but it was approximately these things:

    Explicit schema
    Transactions
    Strong consistency
    Joins, secondary indexes, unique keys, etc.
    The SQL language itself

Looking through the lens of scalability, let's consider the effect of these. Which were the dirty bathwater, and which the baby?

(OP here) Thanks for the thoughtful comment!

Yes, you are right. To rephrase, you say that a browser could first increment its clock to the value larger that the backends, and then synchronize and "win" with the backend, setting the backend value to some bogus "none".

I'd say that it's "fine" in a way that the browser and the backend agree to "something" and are in sync. The case we wanted to prevent was that the browser and the backed hold different values and cannot agree which value to converge to.

70+ tech blogs I follow (together with a weekly aggregate): https://github.com/jakub-m/bulletin/blob/mainline/feeds.conf