Repository navigation
Roadmap / Features Planned #265
Copy link
Copy link
Closed
Labels
area:docsDocumentation and adoption guidanceDocumentation and adoption guidancedocumentationImprovements or additions to documentationImprovements or additions to documentationenhancementNew feature or requestNew feature or requestgood first issueGood for newcomersGood for newcomershelp wantedExtra attention is neededExtra attention is neededpriority:p2Medium priority roadmap itemMedium priority roadmap itemquestionFurther information is requestedFurther information is requestedtype:roadmapRoadmap planning and delivery trackingRoadmap planning and delivery tracking
Description
Do you have a Roadmap or Future Features plan?
- deep query execution plan visualizers
- enterprise backup orchestrators
- telemetry
- management dashboard/portal
- Point-in-Time Recovery (PITR): Continuous transaction log shipping.
Without microsecond-level rollback capabilities, application logic bugs or human errors in a high-throughput, sharded cluster carry a high risk of catastrophic data loss. - Automated Data Tiering (Hierarchical Storage): To achieve huge scale while keeping costs low, the engine could natively and transparently offload historical, cold data blocks to object storage (Azure Blob / AWS S3) while retaining active data on local NVMe, without breaking the query routing layer.
- Row-Level and Column-Level Security (RLS/CLS): If building multi-tenant SaaS or compliance-driven architectures, evaluating access policies natively within the SQL execution engine is essential to eliminate data leakage risks before the data reaches your API proxy layer.
- Lets Encrypt Certs ?
Thanks..
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
area:docsDocumentation and adoption guidanceDocumentation and adoption guidancedocumentationImprovements or additions to documentationImprovements or additions to documentationenhancementNew feature or requestNew feature or requestgood first issueGood for newcomersGood for newcomershelp wantedExtra attention is neededExtra attention is neededpriority:p2Medium priority roadmap itemMedium priority roadmap itemquestionFurther information is requestedFurther information is requestedtype:roadmapRoadmap planning and delivery trackingRoadmap planning and delivery tracking
Activity
MPCoreDeveloper commentedon Jun 10, 2026
Thanks for the great questions! Here's the honest status of each feature:
✅ Already Shipped (v1.9.2)
• Row-Level Security (RLS) — live in SharpCoreDB.Server with Enforced/Audit modes and per-tenant discriminator-column filtering. Column-Level Security (CLS/masking) is next on the security roadmap.
• Telemetry — Prometheus-compatible metrics endpoint is already exposed by the server. SharpCoreDB.Projections ships OpenTelemetry-ready projection metrics.
• Management Dashboard — SharpCoreDB.WebViewer is the Razor Pages admin portal. More panels (query stats, live connections, plan viewer) are being added incrementally.
• Query plan infrastructure — QueryPlanCache, ExecutionPlan, and QueryOptimizer all exist internally. A visual EXPLAIN tree in WebViewer is on the near-term list.
🔶 Roadmap — Near-Term
• Let's Encrypt / ACME auto-renewal — Currently only manual PFX/PEM cert paths are supported. ACME integration (via Kestrel + Certes) is planned so self-hosted deployments get automatic cert rotation with zero manual steps.
• Visual Query Execution Plan Explorer — The internal plan model is already there; the WebViewer needs the tree/graph UI to expose it.
• Column-Level Security — Completes the RLS story started in v1.9.2.
• Enterprise Backup Orchestrator — Scheduled full/incremental backups with remote targets (Azure Blob, S3, SFTP) and retention policies. The WAL and RecoveryManager are the foundation.
🔴 Roadmap Longer Term
• Point-in-Time Recovery (PITR) — The distributed TransactionLog and WAL exist, but continuous log shipping and microsecond-targeted restore across the full engine is a significant undertaking. It will be built on top of the backup orchestrator.
• Automated Data Tiering — Cold archival already works for time-series (BucketTier.Hot/Cold). Transparent hot-NVMe → cold-Blob/S3 routing for general page-based storage is on the long-term roadmap and requires storage engine changes.
If any of these are blockers for your use case, open an issue or upvote an existing one — user-driven features get prioritised first. 🙏