Click here to Skip to main content
15,887,683 members
Please Sign up or sign in to vote.
0.00/5 (No votes)
I'm planning to work on a web project that requires concurrency. I have past experience with websockets and would favour using it again, although I've learnt about xamp and jabber and might be willing to explore if they're more viable. I recently learnt about CRDT (from figma) and while, from my perspective, it conceptually addresses the same issues websockets do, I can't find any articles comparing both.

What I have tried:

It seems CRDT and its abstractions come out of the box with support for concurrent editing -- undo, redo -- while websockets is a high level protocol for bidirectional streaming of data strings. Is there anything else that can aid me in reaching a more informed decision on which would be more suitable for my task? What advantages does either have over its counterpart?
Posted
Updated 11-Sep-18 22:48pm
v3

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900