drewridley / nevy Goto Github PK

In Nevy, it will be essential that developers are able to specify custom logic to determine how, when and if a given component change should be synchronized. This tracking issue will contain discussions, possible designs, and the implications of such designs.

Requirements:

• Limited fragmentation of messages
• Ability to defer/expire messages
• O(n) complexity or better. Should integrate with queries to reduce total search space and complexity
• Eventually consistent, ie, changes not streamed should still eventually exist on the client for state that needs to be synchronzied.
• Datastructure agnostic; Nevy should not enforce a particular acceleration structure or mapping for this 'predicated' streaming.
• Entity driven; Messages or events should be optionally entity directed and the predicated logic can be associated with that entity.