Skip to content

Server side CRDT #14

@shanthanu9

Description

@shanthanu9

If we are going to implement server-side CRDT support, we just have to implement the remote functions right? These functions don't use the findNextGreaterIdentifierList. So the server-side implementation is relatively easier than client-side.

But even if we do it, it raises another issue. CRDT will be implemented in two places, client and server-side. So if say make changes in client-side CRDT implementation, we will also have to change the server-side too. The split-up of the dependent code is not nice.

Another possibility is Elixir calling the already implemented client-side JS CRDT. If it is possible, then it is among the simplest solutions. But will this approach have a performance impact?

Metadata

Metadata

Assignees

No one assigned

    Labels

    brainstormNeeds further thinking and analysis

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions