# EventDBX
You’ll appreciate this database system. It lets you spend less time designing schemas and more time writing code that drives your application.
## Overview
EventDBX is an event-sourced, key-value, write-side database system designed to provide immutable, append-only storage for events across various domains. It is ideal for applications requiring detailed audit trails for compliance, complex business processes involving states, and high data integrity levels.
## Getting Started
Follow the steps below to spin up EventDBX locally. The commands assume you installed the CLI globally; if you're contributing to the project, clone the repository and run them from the repo root instead.
The CLI installs as `dbx`. Older releases exposed an `eventdbx` alias, but the primary command is now `dbx`.
1. **Install the CLI**
```bash
# Install prebuilt binaries via shell script
curl --proto '=https' --tlsv1.2 -LsSf https://github.com/thachp/eventdbx/releases/download/v1.13.2/eventdbx-installer.sh | sh
```
```bash
# Install prebuilt binaries via powershell script
powershell -ExecutionPolicy Bypass -c "irm https://github.com/thachp/eventdbx/releases/download/v1.13.2/eventdbx-installer.ps1 | iex"
```
2. **Start the server**
```bash
dbx start --foreground
```
- Omit `--foreground` to daemonise the process.
- Use `--data-dir <path>` to override the default `$HOME/.eventdbx` directory.
- Restriction (schema enforcement) is enabled by default; disable it with `--restrict=false` if you need a permissive environment.
- The server owns the RocksDB lock while it is running; the CLI detects this and automatically proxies write commands through the HTTP API. Stop the daemon only when you need offline tasks like staging or manual maintenance.
- Choose the API surfaces with `--api rest`, `--api graphql`, `--api grpc`, or `--api all` (enable every surface). Persist the selection by editing the `[api]` table in `config.toml`, for example:
```
[api]
rest = true
graphql = true
grpc = true
```
- Default ports can be overridden in `config.toml`:
- REST and GraphQL share the HTTP listener defined by `port` (default `7070`).
- gRPC uses `[grpc].bind_addr` (default `0.0.0.0:7070`, sharing the HTTP listener).
- The CLI socket listens on `[socket].bind_addr` (default `0.0.0.0:6363`).
3. **Define a schema (recommended when running in restricted mode)**
```bash
dbx schema create \
--aggregate patient \
--events patient-added,patient-updated \
--snapshot-threshold 100
```
Omit `--snapshot-threshold` to inherit the default configured in `config.toml` (if any).
4. **Issue a token for CLI access**
```bash
dbx token generate --group admin --user jane --expiration 3600
```
5. **Append an event**
- When the server is running the CLI proxies writes through the REST API automatically. Pass a token with `--token` or set `EVENTDBX_TOKEN` to reuse your own credentials; otherwise the CLI mints a short-lived token for the call.
```bash
dbx aggregate apply person p-002 patient-added \
--field name="Jane Doe" \
--field status=active
```
- You can also call the REST endpoint directly:
```bash
export EVENTDBX_TOKEN=<token from step 4>
curl -X POST http://127.0.0.1:7070/v1/events \
-H "Authorization: Bearer ${EVENTDBX_TOKEN}" \
-H "Content-Type: application/json" \
-d '{
"aggregate_type": "person",
"aggregate_id": "p-002",
"event_type": "patient-added",
"payload": {
"name": "Jane Doe",
"status": "active"
}
}'
```
- If the server is stopped, the same CLI command writes to the local RocksDB store directly.
You now have a working EventDBX instance with an initial aggregate. Explore the [Command-Line Reference](#command-line-reference) for the full set of supported operations.
## Features
- **Flexible JSON payloads**: Events accept arbitrary JSON payloads; scalar values are normalized into strings for state tracking, while structured objects remain fully queryable.
- **Immutable Data Structure**: Once data is entered into EventDBX, it becomes immutable, meaning it cannot be altered or deleted. This characteristic is crucial for applications where the accuracy and traceability of historical data are paramount, such as medical records, financial transactions, and supply chain management. Data can be archived, moving from short-term to long-term storage, but cannot be deleted.
- **Event Sourcing and Replay**: EventDBX is built on the principle of event sourcing, storing all changes to the data as a sequence of events. This allows for the complete replay of events to reconstruct the database's state at any point in time, thereby enhancing data recovery and audit capabilities. Unlike traditional databases that execute update statements to modify data, this system is event-driven. Aggregate state changes are defined in the event object, allowing these events to be replayed at any time to reconstruct the aggregate's current state.
- **Merkle Tree Integration**: Each aggregate in EventDBX is associated with a Merkle tree of events, enabling verification of data integrity. The Merkle tree structure ensures that any data tampering can be detected, offering an additional security layer against data corruption.
- **Built-in Audit Trails**: EventDBX automatically maintains a comprehensive audit trail of all transactions, a feature invaluable for meeting compliance and regulatory requirements. It provides transparent and tamper-evident records. During audits, administrators can issue specific tokens to auditors to access and review specific aggregate instances and all relevant events associated with those instances.
- **Security with Token-Based Authorization**: EventDBX implements token-based authorization to manage database access. This approach allows for precise control over who can access and modify data, protecting against unauthorized changes.
- **Encrypted Payloads & Secrets at Rest**: Event payloads, aggregate snapshots, and `tokens.json` are encrypted transparently when a DEK is configured. Metadata such as aggregate identifiers, versions, and Merkle roots remain readable so plugins, replication, and integrity checks keep working without additional configuration.
- **Powered by RocksDB and Rust**: At its core, EventDBX utilizes RocksDB for storage, taking advantage of its high performance and efficiency. The system is developed in Rust, known for its safety, efficiency, and concurrency capabilities, ensuring that it is both rapid and dependable.
## Restriction Modes
EventDBX can run in two validation modes, tuned for different phases of development:
- **Unrestricted mode** (`--restrict=false`): Ideal for prototyping and rapid application development. Event payloads are accepted as-is with no schema definition or data-type friction, letting you iterate quickly without pre-registering aggregates, tables, or column types.
- **Restricted mode** (default): Enables schema enforcement. Once your application matures, define required fields, data types, and validation rules via `dbx schema …` commands. Incoming events must match the declared schema, and violations are rejected before they reach storage. You can toggle restriction per server start, so development and production can adopt different policies.
## Command-Line Reference
EventDBX ships a single `dbx` binary. Every command accepts an optional `--config <path>` to point at an alternate configuration file.
### Server lifecycle
- `dbx start [--port <u16>] [--data-dir <path>] [--foreground] [--restrict | --restrict=false]`
Launches the server. Schema validation is enforced by default; pass `--restrict=false` to run in permissive mode.
- `dbx stop`
Stops the running daemon referenced by the PID file.
- `dbx status`
Prints the current port, PID, uptime, and whether restriction is enabled.
- `dbx restart [start options…]`
Stops the existing daemon (if any) and restarts it with the provided options.
- `dbx destroy [--yes]`
Removes the PID file, data directory, and configuration file after confirmation (or immediately with `--yes`).
### Configuration
- `dbx config [--port <u16>] [--data-dir <path>] [--master-key <secret>] [--dek <secret>] [--memory-threshold <usize>] [--list-page-size <usize>] [--page-limit <usize>] [--plugin-max-attempts <u32>]`
Persists configuration updates. Run without flags to print the current settings. The first invocation must include both `--master-key` and `--dek`. `--list-page-size` sets the default page size for aggregate listings (default 10), `--page-limit` caps any requested page size across list and event endpoints (default 1000), and `--plugin-max-attempts` controls how many retries are attempted before an event is marked dead (default 10).
### Tokens
- `dbx token generate --group <name> --user <name> [--expiration <secs>] [--limit <writes>] [--keep-alive]`
Issues a new token tied to a Unix-style group and user.
- `dbx token list`
Lists all tokens with status, expiry, and remaining writes.
- `dbx token revoke --token <value>`
Revokes a token immediately.
- `dbx token refresh --token <value> [--expiration <secs>] [--limit <writes>]`
Extends the lifetime or write allowance of an existing token.
### Schemas
- `dbx schema create --aggregate <name> --events <event1,event2,...> [--snapshot-threshold <u64>]`
- `dbx schema add --aggregate <name> --events <event1,event2,...>`
- `dbx schema remove --aggregate <name> --event <name>`
- `dbx schema list`
Schemas are stored on disk; when the server runs with restriction enabled, incoming events must satisfy the recorded schema.
### Aggregates
- `dbx aggregate apply --aggregate <type> --aggregate-id <id> --event <name> --field KEY=VALUE... [--stage] [--token <value>]`
Appends an event immediately—use `--stage` to queue it for a later commit.
- `dbx aggregate list [--skip <n>] [--take <n>] [--stage]`
Lists aggregates with version, Merkle root, and archive status; pass `--stage` to display queued events instead.
- `dbx aggregate get --aggregate <type> --aggregate-id <id> [--version <u64>] [--include-events]`
- `dbx aggregate replay --aggregate <type> --aggregate-id <id> [--skip <n>] [--take <n>]`
- `dbx aggregate verify --aggregate <type> --aggregate-id <id>`
- `dbx aggregate snapshot --aggregate <type> --aggregate-id <id> [--comment <text>]`
- `dbx aggregate archive --aggregate <type> --aggregate-id <id> [--comment <text>]`
- `dbx aggregate restore --aggregate <type> --aggregate-id <id> [--comment <text>]`
- `dbx aggregate remove --aggregate <type> --aggregate-id <id>` Removes an aggregate that has no events (version still 0).
- `dbx aggregate commit`
Flushes all staged events in a single atomic transaction.
- `dbx aggregate export [<type>] [--all] --output <path> [--format csv|json] [--zip] [--pretty]`
Writes the current aggregate state (no metadata) as CSV or JSON. Exports default to one file per aggregate type; pass `--zip` to bundle the output into an archive.
Staged events are stored in `.eventdbx/staged_events.json`. Use `aggregate apply --stage` to add entries to this queue, inspect them with `aggregate list --stage`, and persist the entire batch with `aggregate commit`. Events are validated against the active schema (when restriction is enabled) during both staging and commit. The commit operation writes every pending event in one RocksDB batch, guaranteeing all-or-nothing persistence.
### Plugins
- `dbx plugin install <plugin> <version> --source <path|url> [--bin <file>] [--checksum <sha256>] [--force]`
- `dbx plugin config tcp --name <label> --host <hostname> --port <u16> [--disable]`
- `dbx plugin config http --name <label> --endpoint <host|url> [--https] [--header KEY=VALUE]... [--disable]`
- `dbx plugin config grpc --name <label> --endpoint <host|url> [--disable]`
- `dbx plugin config log --name <label> --level <trace|debug|info|warn|error> [--template "text with {aggregate} {event} {id}"] [--disable]`
- `dbx plugin config process --name <instance> --plugin <id> --version <semver> [--arg <value>]... [--env KEY=VALUE]... [--working-dir <path>] [--disable]`
- `dbx plugin enable <label>`
- `dbx plugin disable <label>`
- `dbx plugin remove <label>`
- `dbx plugin test`
- `dbx plugin list`
- `dbx plugin queue`
- `dbx plugin queue clear`
- `dbx plugin queue retry [--event-id <uuid>]`
- `dbx plugin replay <plugin-name> <aggregate> [<aggregate_id>]`
Clearing dead entries prompts for confirmation to avoid accidental removal. Manual retries run the failed events immediately; use `--event-id` to target a specific entry.
### Replication
- `dbx remote add <name> <ip> --public-key <base64> [--port <n>]`
Registers a standby and pins its Ed25519 public key. The CLI formats the IP and port into a `tcp://` endpoint (default port `6363`).
- `dbx remote rm <name>`
Removes a configured remote.
- `dbx remote ls`
Lists remotes with their endpoints.
- `dbx remote show <name>`
Displays the endpoint and pinned key for a remote.
- `dbx remote key [--show-path]`
Prints this node's replication public key (generated on first run).
- `dbx push <name> [--dry-run] [--schema] [--schema-only] [--batch-size <n>] [--aggregate <type>...] [--aggregate-id <type:id>...]`
Streams local events to the remote in fast-forward mode; dry runs report pending changes.
- `dbx pull <name> [--dry-run] [--schema] [--schema-only] [--batch-size <n>] [--aggregate <type>...] [--aggregate-id <type:id>...]`
Fast-forwards the local node from the remote, reporting changes in dry-run mode.
Replication keys live alongside the data directory (`replication.key` / `replication.pub`) and are created automatically the first time the CLI loads configuration. The Cap'n Proto listener that powers CLI automation and replication defaults to `[socket].bind_addr` (default `0.0.0.0:6363`); point remotes at that address with a `tcp://` endpoint or override the bind address in `config.toml` when you expose the replica on another interface. The `dbx push` and `dbx pull` commands connect over this socket—no gRPC listener is required—and every session is authenticated with the remote's pinned Ed25519 public key. Use `--aggregate` repeatedly to scope push/pull to specific aggregate types when you only need to sync a subset of data, `--aggregate-id TYPE:ID` to target individual aggregates, `--schema` to copy schema definitions alongside events, and `--schema-only` to synchronize schemas without touching event data.
### Upgrades
- `dbx upgrade [<version>|latest] [--print-only]`
Downloads and runs the platform-specific installer to switch binaries. The CLI looks up releases from GitHub, so you can use `latest` or supply a tag like `v1.13.2` (omitting the leading `v` also works). Versions lower than `v1.13.2` are rejected because upgrades are unsupported before that release. Use `--print-only` to show the command without executing it. Shortcut syntax `dbx upgrade@<version>` resolves through the same lookup.
- `dbx upgrade list [--limit <n>] [--json]`
Queries the GitHub releases API and prints the most recent versions. The default limit is 20; use `--json` for a machine-readable list, and call `dbx upgrade@list` for the same shortcut.
### Maintenance
- `dbx backup --output <path> [--force]`
Creates a compressed archive with the entire EventDBX data directory and configuration. Stop the server before running a backup to avoid partial snapshots.
- `dbx restore --input <path> [--data-dir <path>] [--force]`
Restores data from a backup archive. Use `--data-dir` to override the stored location, and `--force` to overwrite non-empty destinations. The server must be stopped before restoring.
Plugins fire after every committed event to keep external systems in sync. Remaining plugins deliver events through different channels:
- **TCP** – Writes a single-line JSON `EventRecord` to the configured socket.
- **HTTP** – POSTs the `EventRecord` JSON to an endpoint with optional headers; add `--https` during configuration to force HTTPS when the endpoint lacks a scheme.
- **gRPC** – Sends `EventRecord` batches to a remote gRPC endpoint compatible with the replication `ApplyEvents` API.
- **Log** – Emits a formatted line via `tracing` at the configured level. By default: `aggregate=<type> id=<id> event=<event>`.
- **Process** – Launches an installed plugin binary as a supervised subprocess and streams events to it over Cap'n Proto. Use this for first-party plugins from the [`dbx_plugins`](https://github.com/thachp/dbx_plugins) workspace or your own extensions.
Process plugins are distributed as zip/tar bundles. Install them with `dbx plugin install <plugin> <version> --source <path-or-url>`—the bundle is unpacked to `~/.eventdbx/plugins/<plugin>/<version>/<target>/`, where `<target>` matches the current OS/architecture (for example, `x86_64-apple-darwin`). Official bundles live in the `dbx_plugins` releases; pass the asset URL to `--source` or point it at a local build while developing. After installation, bind the binary to an instance:
```bash
dbx plugin config process \
--name search \
--plugin dbx_search \
--version 1.0.0 \
--arg "--listen=0.0.0.0:8081" \
--env SEARCH_CLUSTER=https://example.com
dbx plugin enable search
```
EventDBX supervises the subprocess, restarts it on failure, and delivers every `EventRecord`/aggregate snapshot over the stream. Plugins that run as independent services can continue to use the TCP/HTTP/GRPC emitters instead.
Failed deliveries are automatically queued and retried with exponential backoff. The server keeps attempting until the plugin succeeds or the aggregate is removed, ensuring transient outages do not drop notifications. Use `dbx plugin queue` to inspect pending/dead event IDs.
Plugin configurations are stored in `.eventdbx/plugins.json`. Each plugin instance requires a unique `--name` so you can update, enable, disable, remove, or replay it later. `plugin enable` validates connectivity (creating directories, touching files, or checking network access) before marking the plugin active. Remove a plugin only after disabling it with `plugin disable <name>`. `plugin replay` resends stored events for a single aggregate instance—or every instance of a type—through the selected plugin.
Need point-in-time snapshots instead of streaming plugins? Use `dbx aggregate export` to capture aggregate state as CSV or JSON on demand.
Example gRPC configuration:
```bash
# point at an existing replication-compatible listener
dbx plugin config grpc \
--name audit-grpc \
--endpoint grpc://replica.internal:8800
# enable the plugin once connectivity is confirmed
dbx plugin enable audit-grpc
# inspect status
dbx plugin list
```
Example HTTP/TCP payload (`EventRecord`):
```json
{
"aggregate_type": "patient",
"aggregate_id": "p-001",
"event_type": "patient-updated",
"payload": {
"status": "inactive",
"comment": "Archived via API"
},
"metadata": {
"event_id": "45c3013e-9b95-4ed0-9af9-1a465f81d3cf",
"created_at": "2024-12-01T17:22:43.512345Z",
"issued_by": {
"group": "admin",
"user": "jane"
}
},
"version": 5,
"hash": "cafe…",
"merkle_root": "deadbeef…"
}
```
## REST API
The server exposes a small HTTP API (served on port `7070` by default). All endpoints require a bearer token unless otherwise noted.
| Method & Path | Description |
| ----------------------------------------------------------- | ----------------------------------------------------------------- |
| `GET /health` | Liveness probe (unauthenticated). |
| `GET /v1/aggregates` | Lists aggregates; supports `skip`/`take` query parameters. |
| `GET /v1/aggregates/{aggregate_type}/{aggregate_id}` | Returns the current state for a specific aggregate. |
| `GET /v1/aggregates/{aggregate_type}/{aggregate_id}/events` | Lists events for an aggregate; supports `skip`/`take` pagination. |
| `POST /v1/events` | Appends an event; aggregate identifiers are provided in the body. |
| `GET /v1/aggregates/{aggregate_type}/{aggregate_id}/verify` | Computes and returns the Merkle root for integrity verification. |
Paginated responses cap `take` at the configurable `page_limit` (default `1000`). Adjust it with `dbx config --page-limit <n>` if you need larger pages.
All authenticated requests must include `Authorization: Bearer <token>` with a token issued via the CLI.
### cURL examples
```bash
# Post a JSON event (global endpoint)
curl \
-X POST \
-H "Authorization: Bearer TOKEN" \
-H "Content-Type: application/json" \
-d '{
"aggregate_type": "patient",
"aggregate_id": "p-001",
"event_type": "patient-updated",
"payload": {
"status": "inactive",
"meta": {"source": "api"}
}
}' \
http://localhost:7070/v1/events
# Retrieve the first 10 events for an aggregate (supports `skip`/`take` up to `page_limit`)
curl \
-H "Authorization: Bearer TOKEN" \
"http://localhost:7070/v1/aggregates/patient/p-001/events?skip=0&take=10"
# Health check
curl http://localhost:7070/health
# List aggregates (replace TOKEN with an active value)
curl \
-H "Authorization: Bearer TOKEN" \
http://localhost:7070/v1/aggregates
# Append an event (global endpoint)
curl \
-X POST \
-H "Authorization: Bearer TOKEN" \
-H "Content-Type: application/json" \
-d '{
"aggregate_type": "patient",
"aggregate_id": "p-001",
"event_type": "patient-updated",
"payload": {
"status": "inactive",
"comment": "Archived via API"
}
}' \
http://localhost:7070/v1/events
```
## gRPC API
Enable the gRPC surface by setting `[api] grpc = true` in `config.toml`. The `[grpc]` table configures the bind address (default `0.0.0.0:7070`, reusing the HTTP listener). The service mirrors the REST operations (`AppendEvent`, `ListAggregates`, `GetAggregate`, `ListEvents`, and `VerifyAggregate`) plus a simple `Health` probe.
Example `grpcurl` invocation:
```bash
grpcurl -H "authorization: Bearer TOKEN" \
-d '{
"aggregate_type": "patient",
"aggregate_id": "p-001",
"event_type": "patient-updated",
"payload_json": "{\"status\":\"inactive\"}"
}' \
-plaintext 127.0.0.1:7070 dbx.api.EventService/AppendEvent
```
## GraphQL API
GraphQL is served on `/graphql`, and an interactive Playground is available via `GET /graphql` or `/graphql/playground`. Supply the same bearer token header used for REST requests.
### Query example
```bash
curl -X POST \
-H "Authorization: Bearer TOKEN" \
-H "Content-Type: application/json" \
-d '{
"query": "query RecentAggregates($take: Int!) { aggregates(take: $take) { aggregate_type aggregate_id version merkle_root state } }",
"variables": { "take": 5 }
}' \
http://localhost:7070/graphql
```
Sample response:
```json
{
"data": {
"aggregates": [
{
"aggregate_type": "patient",
"aggregate_id": "p-001",
"version": 3,
"merkle_root": "8f4c3d…",
"state": {
"name": "Jane Doe",
"status": "active"
}
}
]
}
}
```
### Mutation example
```bash
curl -X POST \
-H "Authorization: Bearer TOKEN" \
-H "Content-Type: application/json" \
-d '{
"query": "mutation Append($input: AppendEventInput!) { appendEvent(input: $input) { aggregate_type aggregate_id version payload } }",
"variables": {
"input": {
"aggregate_type": "patient",
"aggregate_id": "p-001",
"event_type": "patient-updated",
"payload": { "status": "inactive", "comment": "Archived via GraphQL" }
}
}
}' \
http://localhost:7070/graphql
```
The mutation triggers the same validation, replication, and plugin notifications as the REST endpoint.
## Contributing
### **Quick Start**
1. **Report Issues**: Found a bug or have a suggestion? [Open an issue](https://chat.openai.com/g/g-kvXdAN8VA-eventdbx-guide/c/72d2fa39-c3e2-4e40-bd61-5694f7b82aab#) with detailed information.
2. **Contribute Code**:
- **Fork & Clone**: Fork the EventDBX repo and clone your fork.
- **Branch**: Create a branch for your changes from **`develop`**.
- **Develop**: Make your changes, adhering to our coding standards. Add or update tests as necessary.
- **Commit**: Use [Conventional Commits](https://www.conventionalcommits.org/) for clear, structured commit messages (e.g., **`feat: add new feature`** or **`fix: correct a bug`**).
- **Pull Request**: Submit a pull request (PR) against the **`develop`** branch of the original repo. Describe your changes and link to any related issues.
### **Guidelines**
- **Formatting**: A project-wide Prettier configuration lives at `.prettierrc.json`; use it for Markdown/JSON/YAML changes.
- **Commit linting**: Conventional Commit headers are enforced through `.commitlintrc.json`.
- **Code Review**: Your PR will be reviewed by the team. Be open to feedback and make requested adjustments.
- **Merge**: Once approved, your PR will be merged into the project, and you'll be credited as a contributor.
## License
---
© 2025 Patrick Thach and contributors
EventDBX is open source software licensed under the [MIT License](./LICENSE).
See the LICENSE file in the repository for details.