4 ms·
How does this compare to something like ShareDB (https://github.com/share/sharedb https://github.com/share/sharedb)? It seems on the face of it that the data pa
by oakesm9 10y ago
How does this compare to something like ShareDB (https://github.com/share/sharedb https://github.com/share/sharedb)? It seems on the face of it that the data part of it is pretty similar (albeit Deepstream is more fully featured with auth etc.), however, there is no mention of how Deepstream handles conflict resolution if two clients are modifying the state.
Internally ShareDB uses Operational Transformation with special operations which are designed for use in JSON documents.
Does anyone know how this works in Deepstream?
- wolframhempel 10y agoThere's a choice of merge algorithms as well as the ability to hook in your own. https://deepstream.io/tutorials/core/handling-data-conflicts/ https://deepstream.io/tutorials/core/handling-data-conflicts...
- oakesm9 10y agoThanks! I hadn't found that before. Sounds like having those merge algorithms/hooks and splitting up the document into multiple "records" might actually be enough for my use case.