Products
Legacy Interlay Mirror Mode
Interlay Mirror Mode remains available for best-effort primary-to-secondary mirroring and is unchanged by Crucible continuous runs. New head-to-head evaluations should use the dedicated /api/v1/endpoint-comparisons arena, run, evidence, and completion APIs.
Configuration
json
{
"settings": {
"mirror": {
"enabled": true,
"mode": "mirror",
"mirror_endpoint_uuids": ["secondary-endpoint-uuid"],
"mirror_reads": true,
"mirror_writes": false,
"sample_ratio": 0.1,
"max_in_flight_per_mirror": 128
}
}
}| Field | Purpose |
|---|---|
enabled | Turns legacy mirror dispatch on for the interlay. |
mode | Use mirror in the open-source runtime. |
mirror_endpoint_uuids | Secondary endpoints that receive mirrored traffic. |
mirror_reads and mirror_writes | Select eligible request classes. |
sample_ratio | Limits how much eligible traffic is mirrored, from 0.0 to 1.0. |
max_in_flight_per_mirror | Bounds asynchronous work for each secondary endpoint. |
Validation Rules
Eden resolves mirrors within the same organization and rejects a Mirror Mode configuration when the mirror list is empty or duplicated, the primary appears as a mirror, a mirror is not the same endpoint kind as the primary, or either the primary or a mirror is not a direct endpoint. The primary migration target also cannot appear in the mirror list.
Protocol Coverage
| Endpoint kind | Current comparison behavior |
|---|---|
| Redis | Eligible requests are mirrored through the unified Redis processor. |
| PostgreSQL | Simple-query traffic is comparable; extended-query batches and session-affine traffic are primary-only and recorded as skips. |
| MongoDB | Parsed commands are comparable; transaction-shaped requests are primary-only and recorded as skips. |
| MySQL | Comparable request handling emits the same protocol-neutral mirror evidence. |