ROADMAP.md

Timeseries Module Roadmap

Current Status

Production-capable timeseries runtime exists for ingest, Gorilla compression, adaptive flush, query/downsampling, retention, remote-write, and encrypted chunk handling.

In Progress

• [~] hardening adaptive flush and high-ingest behavior under sustained concurrency pressure (Target: Q3 2026)
• [~] improving diagnostics consistency across ingest, query, and retention stages (Target: Q3 2026)
• [~] stabilizing benchmark-backed release guardrails for timeseries hot paths (Target: Q3 2026)

Planned Features

Short-term (3-6 months)

• tighten deterministic behavior for remote-write and encrypted chunk edge scenarios (Target: Q4 2026)
• expand stress coverage for mixed ingest/query/downsampling workloads (Target: Q4 2026)
• improve operator-facing diagnostics for retention and flush incidents (Target: Q4 2026)

Mid-term (6-12 months)

• re-baseline p95/p99 envelopes for ingest, range-query, and flush-sensitive paths (Target: Q1 2027)
• broaden benchmark depth for remote-write and lifecycle workload diversity (Target: Q1 2027)
• harden long-run reliability under sustained timeseries load (Target: Q1 2027)

Implementation Phases

Phase 1: Design / API Contract

• freeze timeseries ingest/query/lifecycle contracts for current major line (Target: Q3 2026)
• define explicit error taxonomy for flush, query, and retention incidents (Target: Q3 2026)

Phase 2: Core Implementation

• complete hardening for TSStore, flush controller, and query internals (Target: Q4 2026)
• align encrypted chunk and remote-write behavior to bounded runtime contracts (Target: Q4 2026)

Phase 3: Error Handling and Edge Cases

• standardize fail-safe behavior for buffer pressure, retention faults, and remote-write validation errors (Target: Q4 2026)
• unify diagnostics across ingest, lifecycle, and integration incident classes (Target: Q4 2026)

Phase 4: Tests

• expand focused regressions for adaptive flush, range-query, and encryption edge scenarios (Target: Q4 2026)
• extend deterministic stress fixtures for concurrent ingest/query workloads (Target: Q4 2026)

Phase 5: Performance and Hardening

• lock benchmark-backed release gates for timeseries hot paths (Target: Q4 2026)
• validate p95/p99 and throughput behavior against release baselines (Target: Q4 2026)

Phase 6: Documentation and Acceptance

• core timeseries module docs aligned to source-verifiable behavior
• roadmap/future planning separated from historical changelog entries

Production Readiness Checklist

• core timeseries surfaces documented and source-verified
• module-level security and failure behavior documented
• benchmark mapping documented in performance expectations
• remaining hardening tasks closed for ingest/flush/lifecycle edge paths
• release benchmark stabilization complete

Known Issues and Limitations

• runtime behavior depends on workload shape, flush configuration, and storage profile.
• selected flush, retention, and encrypted chunk edge scenarios need continued hardening.
• benchmark depth should continue expanding for broader timeseries workloads.

Breaking Changes

No breaking timeseries contract planned. Any contract-breaking change requires migration notes and changelog entry before merge.