All Classes and Interfaces
Class
Description
Service discovery protocol version.
Endpoint
ProtocolMode
Interface to abstract setting the logging context variables.
Handler
HandlerType
InputPayload
Custom metadata of this handler definition.
Custom metadata of this service definition.
OutputPayload
Completable: Yes
Fallible: Yes
Type: 0x0400 + 12
Completable: Yes
Fallible: Yes
Type: 0x0400 + 12
Notification for AttachInvocationCommandMessage
Type: 0x8000 + 12
Notification for AttachInvocationCommandMessage
Type: 0x8000 + 12
Protobuf enum
dev.restate.service.protocol.BuiltInSignal
Completable: Yes (two notifications: one with invocation id, then one with the actual result)
Fallible: Yes
Type: 0x0400 + D
Completable: Yes (two notifications: one with invocation id, then one with the actual result)
Fallible: Yes
Type: 0x0400 + D
Notification for CallCommandMessage
Type: 0x8000 + D
Notification for CallCommandMessage
Type: 0x8000 + D
Notification for CallCommandMessage and OneWayCallCommandMessage
Type: 0x8000 + E
Notification for CallCommandMessage and OneWayCallCommandMessage
Type: 0x8000 + E
Completable: No
Fallible: No
Type: 0x0400 + 5
Completable: No
Fallible: No
Type: 0x0400 + 5
Completable: No
Fallible: No
Type: 0x0400 + 4
Completable: No
Fallible: No
Type: 0x0400 + 4
Type: 0x0000 + 4
Type: 0x0000 + 4
We have this for backward compatibility, because we need to parse both old and new awakeable id.
We have this for backward compatibility, because we need to parse both old and new awakeable id.
Completable: Yes
Fallible: No
Type: 0x0400 + B
Completable: Yes
Fallible: No
Type: 0x0400 + B
Notification for CompletePromiseCommandMessage
Type: 0x8000 + B
Notification for CompletePromiseCommandMessage
Type: 0x8000 + B
Type: 0x0000 + 3
Implementations MUST send this message when the invocation lifecycle ends.
Type: 0x0000 + 3
Implementations MUST send this message when the invocation lifecycle ends.
Type: 0x0000 + 2
Type: 0x0000 + 2
This failure object carries user visible errors,
e.g.
This failure object carries user visible errors,
e.g.
Completable: No
Fallible: No
Type: 0x0400 + 7
Completable: No
Fallible: No
Type: 0x0400 + 7
Completable: No
Fallible: No
Type: 0x0400 + 8
Completable: No
Fallible: No
Type: 0x0400 + 8
Completable: Yes
Fallible: Yes
Type: 0x0400 + 13
Completable: Yes
Fallible: Yes
Type: 0x0400 + 13
Notification for GetInvocationOutputCommandMessage
Type: 0x8000 + 13
Notification for GetInvocationOutputCommandMessage
Type: 0x8000 + 13
Completable: Yes
Fallible: No
Type: 0x0400 + 2
Completable: Yes
Fallible: No
Type: 0x0400 + 2
Notification for GetLazyStateCommandMessage
Type: 0x8000 + 2
Notification for GetLazyStateCommandMessage
Type: 0x8000 + 2
Completable: Yes
Fallible: No
Type: 0x0400 + 6
Completable: Yes
Fallible: No
Type: 0x0400 + 6
Notification for GetLazyStateKeysCommandMessage
Type: 0x8000 + 6
Notification for GetLazyStateKeysCommandMessage
Type: 0x8000 + 6
Completable: Yes
Fallible: No
Type: 0x0400 + 9
Completable: Yes
Fallible: No
Type: 0x0400 + 9
Notification for GetPromiseCommandMessage
Type: 0x8000 + 9
Notification for GetPromiseCommandMessage
Type: 0x8000 + 9
Protobuf type
dev.restate.service.protocol.HeaderProtobuf type
dev.restate.service.protocol.HeaderProtobuf type
dev.restate.service.protocol.IdempotentRequestTargetProtobuf type
dev.restate.service.protocol.IdempotentRequestTarget
Completable: No
Fallible: No
Type: 0x0400 + 0
Completable: No
Fallible: No
Type: 0x0400 + 0
A notification message follows the following duck-type:
A notification message follows the following duck-type:
Completable: Yes (only one notification with invocation id)
Fallible: Yes
Type: 0x0400 + E
Completable: Yes (only one notification with invocation id)
Fallible: Yes
Type: 0x0400 + E
Completable: No
Fallible: No
Type: 0x0400 + 1
Completable: No
Fallible: No
Type: 0x0400 + 1
Completable: Yes
Fallible: No
Type: 0x0400 + A
Completable: Yes
Fallible: No
Type: 0x0400 + A
Notification for PeekPromiseCommandMessage
Type: 0x8000 + A
Notification for PeekPromiseCommandMessage
Type: 0x8000 + A
This is a special control message to propose ctx.run completions to the runtime.
This is a special control message to propose ctx.run completions to the runtime.
Proposals for Run completions are sent through ProposeRunCompletionMessage
Completable: Yes
Fallible: No
Type: 0x0400 + 11
Proposals for Run completions are sent through ProposeRunCompletionMessage
Completable: Yes
Fallible: No
Type: 0x0400 + 11
Notification for RunCommandMessage
Type: 0x8000 + 11
Notification for RunCommandMessage
Type: 0x8000 + 11
Completable: No
Fallible: Yes
Type: 0x04000 + 10
Completable: No
Fallible: Yes
Type: 0x04000 + 10
Service protocol version.
Completable: No
Fallible: No
Type: 0x0400 + 3
Completable: No
Fallible: No
Type: 0x0400 + 3
Notification message for signals
Type: 0xFBFF
Notification message for signals
Type: 0xFBFF
Completable: Yes
Fallible: No
Type: 0x0400 + C
Completable: Yes
Fallible: No
Type: 0x0400 + C
Notification for SleepCommandMessage
Type: 0x8000 + C
Notification for SleepCommandMessage
Type: 0x8000 + C
Type: 0x0000 + 0
Type: 0x0000 + 0
Protobuf type
dev.restate.service.protocol.StartMessage.StateEntryProtobuf type
dev.restate.service.protocol.StartMessage.StateEntryProtobuf type
dev.restate.service.protocol.StateKeysProtobuf type
dev.restate.service.protocol.StateKeys
Type: 0x0000 + 1
Implementations MUST send this message when suspending an invocation.
Type: 0x0000 + 1
Implementations MUST send this message when suspending an invocation.
Protobuf type
dev.restate.service.protocol.ValueProtobuf type
dev.restate.service.protocol.ValueProtobuf type
dev.restate.service.protocol.VoidProtobuf type
dev.restate.service.protocol.VoidProtobuf type
dev.restate.service.protocol.WorkflowTargetProtobuf type
dev.restate.service.protocol.WorkflowTargetResolved handler for an invocation.
Log4j2
ContextDataProvider inferring context from HandlerRunner.HANDLER_CONTEXT_THREAD_LOCAL.Service
ServiceType
More or less same as the VM trait