Why NoSQL
I feel like I&#x27;m missing something in this article. Several of the points just don&#x27;t make any sense to me.<p>* Their point about how you can just rewrite relational queries manually and not lose any performance does not seem true the moment that you need to join tables on a condition.<p>* Their section on reliable replications can be resolved by keeping a log of the changes made to the database rather than a log of the queries. I don&#x27;t understand how their NoSql model of &quot;Download the latest doc during a change&quot; is any better. It basically becomes &quot;last writer wins&quot; in a distributed system.<p>* The downgrading to NoSql argument makes little sense to me as well. If your frontend is sqlite then you can have Postgres, or MariaDb in your backend. You need to account for having different queries on the front and the back, but the backend is presumably also operating under very different constraints than the frontend.<p>* I&#x27;d actually make an argument that NoSql databases are a type of relational database heavily optimized towards not needing to do joins. The corollary to this is that over time you may find that, oops, you do want to do joins, and now you have to pay a tax on not being set up to do so in the first place.<p>* Also, is it just me or is the Hybrid Logical Clock they mention a type of Lamport Clock where the linked article doesn&#x27;t ever state that?