3 ms·
I think the argument is that people expect mobile and client-side web apps to continue working offline, and eventually sync and merge changes across clients. So
by ProblemFactory 9y ago
I think the argument is that people expect mobile and client-side web apps to continue working offline, and eventually sync and merge changes across clients. So you need a good solution for resolving inconsistent updates made by two offline clients. The same solution could be used for resolving inconsistent updates made on two database servers.
- marknadal 9y agoThis is so beautifully said, I wish I could have been that concise. Thank you for this comment, very well worded. That is exactly what I'm trying to do with my own system, for anybody curious: https://github.com/amark/gun https://github.com/amark/gun (MIT / ZLIB / Apache 2 licensed).
- aidenn0 9y agoOkay, that makes sense.
- naasking 9y ago> So you need a good solution for resolving inconsistent updates made by two offline clients. The same solution could be used for resolving inconsistent updates made on two database servers. Exactly what I was trying to get at, thanks. The line between client state, server state and db state is a thin illusion. As REST makes explicit, every client operates on a representation of some server resources, which means CAP can come into play in even the most trivial online apps.
- deleted 9y ago[deleted]