A Conflict-Free Replicated JSON Datatype
It is impossible to have accurate conflict-free replicated data. Unless the users are given the opportunity to manually resolve conflicts, it will never be 100% accurate - Incorrect data will creep in from time to time (but at least the incorrect data will be consistent across all nodes).<p>The root of the problem is that the system cannot understand the collaborative intent of concurrent users - If you have 2 users who made a change at the same time (without being aware of each other); you have to account for the fact that maybe UserB would have behaved differently if they had been aware of UserA&#x27;s input (which happened at the same time while one or both users were offline). If the user has been offline for a while - Many such conflicts could arise (maybe by the time the internet comes back on, the user is looking at a completely different page than the one they made the change on) and it&#x27;s tedious to make the user resolve them all manually.<p>Also with this approach, it tends to force you to keep a copy&#x2F;cache of all the data in your entire app (for that logged-in user) on the frontend - If you have a big app with lots of pages, that could consume a lot of memory.<p>There are cases where the best solution is to simply tell the user &quot;Sorry, you do not have an internet connection at the moment, so you cannot modify this data&quot; rather than giving them a false sense that the data are correctly backed up in the cloud. I think with CRDTs, it&#x27;s really important to inform the user when they are offline and when their data are not synced&#x2F;backed up in the cloud (so they don&#x27;t get any bad surprises when the internet suddenly comes back on).<p>CRDTs are good where the accuracy of the data is not critical (E.g. bank transactions). One could argue that they improve the user experience, but at the core, developers like them because they make life easier.