You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It should be possible to clone one zell over multiple dishes. This is mainly for optimiz ation but I think it's crucial, especially in combination with automatic migration. Together it would allow a dish to "download" any zell and thus shorten response times significantly. It would also allow to distribute larger content over the network and to easily archive zells.
I imagine that an event-sourced approach might work well here. A single clone receives a messages, executes a command and if accepted, publishes an event notification which is sent to all clones. The tricky part is conflict resolution. Different generic strategies could be supported by he library but in the end, it's very much use-case specific. But it needs to be assured that all clones reach a consistent state eventually.
The text was updated successfully, but these errors were encountered:
It should be possible to clone one zell over multiple dishes. This is mainly for optimiz ation but I think it's crucial, especially in combination with automatic migration. Together it would allow a dish to "download" any zell and thus shorten response times significantly. It would also allow to distribute larger content over the network and to easily archive zells.
I imagine that an event-sourced approach might work well here. A single clone receives a messages, executes a command and if accepted, publishes an event notification which is sent to all clones. The tricky part is conflict resolution. Different generic strategies could be supported by he library but in the end, it's very much use-case specific. But it needs to be assured that all clones reach a consistent state eventually.
The text was updated successfully, but these errors were encountered: