Implement cloudstate.crdt.Crdt Service

[marcellanz]

Implement the cloudstate.crdt.Crdt Service from protobuf/protocol/cloudstate/crdt.proto

Tasks

• CRDT Service
  • State Handling
  • Command Handling
    • Non-Streamed
    • Streamed
  • Cancellation
  • "Callbacks"
  • Context API
• GCounter
• PNCounter
• GSet
• ORSet
• Flag
• LWWRegister
• ORMap
• Vote
• apply new context based API to the evensourced API
• verify implementation (TCK, CrdtSpecs(?))
  • Currently blocked by Evolve the TCK cloudstate#316, but marking progress on the issue to have a
    TCK capable to verify the CRDT state model.
  • TCK verification is replaced by functional tests.
• presence example
• paradox documentation => see CRDT Antora documentation #36
• Optional: provide CRDT protocol spec feedback (mainly for clarification without reading the implementation)

WIP-branch
https://github.com/cloudstateio/go-support/tree/feature/crdt_support

[marcellanz]

Working on it.

[viktorklang]

@marcellanz Very cool, Marcel! (Ping @jroper)

[viktorklang]

Woot! very nice progress here, @marcellanz!

[sleipnir]

Awesome @marcellanz

[marcellanz]

Input from #27:

in future, we may add features to Cloudstate where we start up additional versions of the same entity, for example, we might offer some built in temporal loading support, where users can say "run this command against this entity in the state that it was in at this point of time in history". To do that, we would create a new entity context for that, even if an existing one already existed on that node, and replay the journal up until that time before running the command.

The current CRDT runner should do the same for EventSourcing and any other state model.

[marcellanz]

TCK verification is replaced by functional tests.

[marcellanz]

"Optional: provide CRDT protocol spec feedback (mainly for clarification without reading the implementation)" is captured in a separate issue: #40