event_log

Category: Queues and messaging
Wire type: event_log
Construction: CREATE

Queue and messaging types provide ordering, delivery, streaming, and publication semantics.

Create a value

Use the top-level CREATE command to initialize this structured value. The example shows its construction options.

amaquet-cli -uri amaquet://127.0.0.1:13378 CREATE '{"key":"example:event_log","type":"event_log","options":{}}'

Construction options

Example CREATE options: {}. Omitted fields use server defaults.

Supported operations

APPEND, READ, LEN.

See the complete operation contract for exact arguments, defaults, results, and whether a listed GET is the top-level key command or a type-specific OP. It also identifies read-only operations and documents validation, lazy maintenance, and key-version behavior.

Operation payloads

The following examples use the public amaquet-cli JSON command format. Replace example:event_log with the key used by your application.

Construction payloads

Use the payload below to initialize this type before issuing reads or type-specific operations.

CREATE

This payload initializes the value and must complete before its type-specific operations are used.

{
  "key": "example:event_log",
  "type": "event_log",
  "options": {}
}

Operations

Each request uses the OP envelope. The response is the type-specific value described in the complete operation contract.

OP APPEND

Accepts event_type, optional aggregate_id, nested payload and returns event with one-based sequence and UTC timestamp.

{
  "key": "example:event_log",
  "operation": "APPEND",
  "args": {
    "event_type": "created",
    "aggregate_id": "agg1",
    "payload": {
      "type": "utf8_string",
      "value": "born"
    }
  }
}

OP LEN

Takes no arguments and returns event count.

{
  "key": "example:event_log",
  "operation": "LEN",
  "args": {}
}

OP READ

Accepts optional from sequence and count; returns events with sequence at or after the requested value.

{
  "key": "example:event_log",
  "operation": "READ",
  "args": {
    "from": 1,
    "count": 100
  }
}

Top-level read payload

GET reads the current value without changing it:

{
  "key": "example:event_log"
}

Key lifecycle payloads

These commands apply to the key regardless of its registered type:

• TYPE: {"key":"example:event_log"} — returns the wire type.
• EXISTS: {"key":"example:event_log"} — reports whether the key exists.
• EXPIRE: {"key":"example:event_log","ttl_ms":5000} — assigns a five-second TTL.
• TTL: {"key":"example:event_log"} — returns the remaining TTL in milliseconds.
• PERSIST: {"key":"example:event_log"} — removes the TTL.
• DEL: {"keys":["example:event_log"]} — deletes the key.

For defaults, validation, result shapes, and persistence classification, see the complete operation contract.

Key lifecycle

The key participates in TYPE, EXISTS, TTL, EXPIRE, PERSIST, and DEL. Top-level GET returns the type’s direct public value or a synchronized snapshot.