Get desktop application:
View/edit binary Protocol Buffers messages
Service to use AxonServer as a provider of an EventScheduler
Cancel the publication of a scheduled event. If the events has already been published, this method does nothing.
Request message to cancel an event
token of scheduled event to cancel
Reschedule a scheduled event and optionally replace it by a new event.
Request message to reschedule an event
schedule token of the event to reschedule
timestamp when to publish the event
optionally provide a new event to publish
Schedule the given event for publication at the given time}. The returned ScheduleToken can be used to reschedule or cancel the planned publication.
Request message to schedule an event
timestamp when to publish the event
the event to publish
Service providing Event Store RPCs supporting DCB.
Assigns tags to the event identified by its sequence.
The request to add tags to the event.
The sequence of the event whose tags list will be expanded with the tags from the request.
The tags to be added to the event. If the event already contains a tag from the same list (with the same key and the value) the new one will be ignored.
The response indicating a successful addition of tags to the event.
(message has no fields)
Appends new events to the store.
The message representing the request to append events to the event store.
The condition used to check the validity of this request. If omitted, events will be appended unconditionally.
A list of tagged events to be appended to the event store if the condition is met. These events are considered as a transaction - they are either all appended or none of them are appended. The event store will index the events based on provided tags for future faster retrieval.
The response of a successful append events request. If there was an issue with the append events request, the stream will complete with an error.
The sequence of the first event stored in the event store. Corresponding to the list of events (a transaction) passed in the AppendEventsRequest.
The number of events appended. Matches the number of events passed in the AppendEventsRequest.
The consistency marker which may be used for a subsequent append events requests. Do note that during the time this consistency marker may get far behind the head of the event store which will increase the time needed for the append events request to be validated. If you don't plan to do subsequent append events requests in a "short" period of time, use the Source RPC to refresh the consistency marker.
Gets the current _head_ of the Event Store. The _head_ points to the sequence of the first event to be appended.
The request to retrieve the current HEAD of the event store.
(message has no fields)
The current HEAD of the event store.
The sequence of the current head. Points to the position of the first event to be appended. The HEAD of an empty event store is 0.
Returns the lowest sequence of an event with a timestamp equal to or higher than the given timestamp. The HEAD is returned if no events exist with a timestamp equal to or higher than the given timestamp. N.B. Axon Server does not assign timestamps to events. The timestamps used for fulfilling this RPC are timestamps provided by the client. It could happen that there are events after the returned sequence that have an earlier timestamp. Axon Server does not reject appends if timestamps of events are not monotonically increasing.
The request to get the sequence of the event whose timestamp is the same as the timestamp provided in the request. If there are no events with the exact timestamp, then the sequence of the first one after the provided timestamp is returned. If the provided timestamp is greater that the sequence of the last event in the event store, the HEAD is returned.
The timestamp.
The sequence of the event approximately close to the provided timestamp.
The sequence of the event.
Gets tags for the event identified by its sequence.
The request to retrieve tags of the event.
The sequence of the event whose tags should be retrieved.
The response containing tags of an event.
The tags associated to the event.
Gets the current _tail_ of the Event Store. The _tail_ points to the sequence of the first event stored.
The request to retrieve the current TAIL of the event store.
(message has no fields)
The current TAIL of the event store.
The sequence of the first event in the event store. 0 for an empty event store. 0 for a non-truncated event store. Non-zero for a truncated event store.
Removes tags from the event identified by its sequence.
The request to remove tags from the event.
The sequence of the event whose tags should be removed.
Tags to be removed. If the event is not tagged with listed tags, they are skipped.
The response indicating a successful removal of tags for the event.
(message has no fields)
Provides a finite stream of events based on the passed SourceEventsRequest.
The request to source events from the event store. It results in a finite stream of events completed by the event store. It may also be cancelled by the client. Only events matching the given criteria (a provided list of criterions) will be present in the stream. The stream is capped by the HEAD of the event store.
An inclusive sequence of the first event to be included in the resulting stream.
The criteria consisting of the list of criterions. If at least one of these criterions is met, the criteria is met.
The response to the SourceEventsRequest. It consists either of an event (with its corresponding sequence) or a consistency marker. The consistency marker should be used in a following AppendEventsRequest related to the criteria used in the SourceEventsRequest this response originates from.
The event matching the criteria with its corresponding sequence.
The consistency marker to be used for the following append related to the same criteria.
Provides an infinite stream of events based on the passed StreamEventsRequest.
The request to provide an infinite stream of events from the event store. The client may cancel the stream at any time.
The inclusive sequence to start streaming from.
The criteria used to filter out events. Represented by a list of criterions. If at least one is met, the whole criteria is met.
The response to the StreamEventsRequest.
The event with its corresponding sequence.
Service providing Snapshot Store RPCs.
Adds a snapshot to the snapshot store.
The request to add the snapshot to the snapshot store.
The key this snapshot is added to.
The sequence of the snapshot. Usually linked to the sequence of the event in the event store up to which the snapshot is taken.
If set to true, older snapshots for the same key are pruned.
The snapshot.
The response indicating the successful addition of the snapshot.
(message has no fields)
Deletes a snapshot from the snapshot store.
The request to delete the snapshot from the snapshot store. Deletes from a sequence of `0` to the specified `to_sequence`
The key the snapshot is identified by.
The exclusive upper bound sequence of the snapshot to end the deletion.
The response indicating the successful deletion of the snapshot.
(message has no fields)
Gets the latest snapshot based on the request from the snapshot store.
The request to retrieve the snapshot with the highest sequence from the snapshot store.
The key of the snapshot.
The response to GetLatestSnapshotRequest.
The key of the snapshot.
The sequence of the snapshot.
The snapshot.
Retrieves snapshots from the snapshot store.
The request to retrieve all snapshots from the snapshot store based on the key and sequence bounds.
The key of the snapshot.
The inclusive bottom bound sequence used to filter out snapshots.
The exclusive upper bound sequence used to filter out snapshots.
The response to the ListSnapshotRequest.
The key of the snapshot.
The sequence of the snapshot.
The snapshot.
Service providing Event Store RPCs supporting DCB combined with snapshots.
Provides a finite stream of events based on the passed SnapshottedSourceRequest, optionally preceded by the latest snapshot stored under the given snapshot key. When a snapshot is present, the stream starts with that snapshot followed by the events with a sequence greater than the snapshot's sequence; otherwise, it behaves like a regular Source RPC starting from the beginning.
The request to source events from the event store, prefixed by the latest matching snapshot if available. It results in a finite stream completed by the event store. It may also be cancelled by the client. Only events matching the given criteria (a provided list of criterions) will be present in the stream. The stream is capped by the HEAD of the event store.
The key used to look up the latest snapshot in the snapshot store. If a snapshot exists for this key, it is emitted as the first response and events are sourced starting from the sequence following that snapshot. If no snapshot exists, events are sourced from the beginning. The server does not validate any relationship between the snapshot key and the provided criteria. It is the caller's responsibility to ensure the snapshot key and criteria refer to the same entity, so that the snapshot represents a state that can be correctly evolved by applying the sourced events.
The criteria consisting of the list of criterions. If at least one of these criterions is met, the criteria is met.
The response to the SnapshottedSourceRequest. It consists either of a snapshot (emitted at most once at the beginning of the stream), an event (with its corresponding sequence), or a consistency marker. The consistency marker should be used in a following AppendEventsRequest related to the criteria used in the SnapshottedSourceRequest this response originates from.
The latest snapshot stored under the snapshot key from the request. When present, it is emitted as the first message of the stream and is followed by events with a sequence greater than the snapshot's sequence.
The event matching the criteria with its corresponding sequence.
The consistency marker to be used for the following append related to the same criteria.
The condition for an AppendEventsRequest. Consists of the consistency marker and the criteria (a list of criterions).
Used in:
The sequence used to start checking for the consistency of an append. If there are events with a sequence greater or equal than the consistency marker and those are matching the given criteria, the condition is not met and the transaction is rejected. Otherwise, it is accepted.
The criteria. Consists of a list of criterions. If a single criterion is met, the whole criteria is met.
The integral part of the criteria.
Used in: , , ,
The criterion based on event tags and event names.
The event message.
Used in: , , ,
The unique identifier of the event.
The timestamp of the event.
The name of the event.
The version of the event.
The payload of the event.
The metadata of the event.
Token to manage a scheduled event
Used as response type in: DcbEventScheduler.RescheduleEvent, DcbEventScheduler.ScheduleEvent
Field defining the token identifier
The event retrieved from the event store with its corresponding sequence.
Used in: , ,
The sequence of the event.
The event.
The snapshot.
Used in: , , ,
The name of the snapshot.
The version of the snapshot.
The payload of the snapshot.
The timestamp of the snapshot.
The metadata of the snapshot.
The tag. Describes an event with more details. Usually using concepts from the Domain.
Used in: , , , ,
The key of the tag.
The value of the tag.
The event described in more details by a list of tags.
Used in:
The event.
List of tags describing the given event in more details.
The criterion based on event tags and event names. The event meets this criterion if ALL tags from this criterion are present in the tags of the event AND if the event name is present in one of the names of the this criterion.
Used in:
A list of event names. The event meets this criterion if its name is in one of the names in this list.
A list of event tags. The event meets this criterion if it contains all the tags from this list. It meets the criterion if it contains more than provided list here, but it MUST contain all from the list.