One endpoint for events and batches.
POST /events accepts a single event or a nonempty array. Each request is atomic and retains input order. Recorded events return after storage confirms durability.
Log
Changes.
In order.
Updates to the event log, HTTP API, and developer tooling.
In developmentOrdered batches. Durable storage.
The writer groups concurrent requests while keeping client batches intact. Readers expose durable events in append order. Configurable limits bound pending requests and accounted bytes.
Durability and failuresIngestion load testing.
The groundhog-load executable exercises durable ingestion through the HTTP API. Trial scripts coordinate workloads and summarize throughput and batch latency for comparison.
The event log.
The initial implementation stores immutable JSON events with a source, ID, and recording timestamp. The HTTP service supports durable append, retrieval by ID, and ordered reads.
API reference