High-Performance Encrypted Database for .NET 11 | Embedded + gRPC Server | Vector Search , GraphRAG , Analytics
Repo MPCoreDeveloper/SharpCoreDB, read from GitHub 1 d ago. MPCoreDeveloper has not joined Take My Repo.
The release candidate of the v2.1 line: net11.0 only, C# 15 preview (LangVersion=preview).
The net10.0 / C# 14 packages remain the v2.0 stable line on master.
Pre-release. NuGet will not select these packages unless you request the version explicitly or tick
Include prerelease in Visual Studio.
dotnet add package SharpCoreDB --version 2.1.0-RC.3
| Gate | Result |
|---|---|
| 16 test suites (core + companions) | 2,897 tests — 0 failed, 0 errors, 16 skipped (core 1,916) |
CI — CI v2.1 Preview (.NET 11) |
green on ubuntu-latest and windows-latest — the first green run since 2026-09-14 |
Write-path regression gate (--gate) |
PASSED (nothing slower than baseline × 1.50) |
| Benchmark arms | comparative, fair-PK, pure default, PageBased and multi-row measured in the product-default regime |
| NuGet publish | 27 packages pushed, all 27 verified live on nuget.org |
CryptoServiceAesGcm per key and AesGcmEncryption one per instance, and both are used from severalAesGcm instance one-shots are not thread-safe off WindowsAesGcm across 12 threads fails withOpenSslCryptographicException: error:1C800066:Provider routines::cipher operation failed, one instanceCryptoService.ResetEncryptionCounter could repeat a GCM nonce. The counter was incremented beforeEncrypt now reads the pair with a seqlock.arena-append calls per row: 3 → 1).DiskAnnIndex with CREATE VECTOR INDEX … USING DISKANN,IVerifiableIndex.Verify(), canonical SHA-256 artifact_id), and two newSharpCoreDB.Search (BM25) and SharpCoreDB.HybridSearch (rank fusion).TryAppendEventsAsync(expectedVersion)).INSERT is still ~1.4× behind SQLite on the fair-PK shape (1.9× on the pure default config);UPDATE is 4.9× behind. Both are tracked with their measurements.NoEncryptMode raw-speed posture on everyNoEncryptMode=true stays the explicit opt-out.src/SharpCoreDB.Server/Dockerfile is net10.0-only, so it cannotnet11.0 projects. The v2.1 tags are therefore excluded from the Docker workflowCI/CD Pipeline, which pins a different SDK) until a net11-aware Dockerfile exists.2.1.0-RC.3)Core SharpCoreDB · server/client SharpCoreDB.Server.Core, SharpCoreDB.Server.Protocol,
SharpCoreDB.Client, SharpCoreDB.Client.Protocol, SharpCoreDB.Data.Provider,
SharpCoreDB.Aspire.Hosting · engines & extensions SharpCoreDB.Extensions, SharpCoreDB.Analytics,
SharpCoreDB.Distributed, SharpCoreDB.Identity, SharpCoreDB.Serilog.Sinks · search & vector
SharpCoreDB.Search (first release), SharpCoreDB.HybridSearch (first release),
SharpCoreDB.VectorSearch, SharpCoreDB.Graph, SharpCoreDB.Graph.Advanced · providers
SharpCoreDB.EntityFrameworkCore, SharpCoreDB.Provider.YesSql, SharpCoreDB.Provider.Sync ·
architecture SharpCoreDB.CQRS, SharpCoreDB.Projections, SharpCoreDB.EventSourcing · functional
SharpCoreDB.Functional, SharpCoreDB.Functional.Dapper, SharpCoreDB.Functional.EntityFrameworkCore,
SharpCoreDB.Functional.Linq2DB
SharpCoreDB.Server is deliberately absent: the server host is IsPackable=false and ships as the
sharpcoredb-server executable / container image.
Full notes, including every measured benchmark arm and the open items:
docs/2.1.0-RC.3_WHAT_CHANGED.md
Full Changelog: v2.0.0.2...v2.0.0.3
Full Changelog: 2.0.0.2...v2.0.0.2
Patch release that ships the WAL FileStream.Position race fix as a 4-part version
(2.0.0.1 — the first patch under the new n.n.n.n versioning).
Position + WriteAsync, while the background write-behindPosition mutation could land WAL bytes on aJsonException '0x02' or "Expected 100 rows, got 0" (seen onVacuumMode.Full reopen in CI).FileStream.Position use is now serialized through SingleFileStorageProvider.WriteAtPosition can never beVacuumStressTests stress suite: create → insert → flush → reopen and VacuumMode.Full2.0.0.1.master (the V2 trunk) and release/v2.0.0.0 both carry this fix.V2 is the performance-first, storage-architecture-complete release. This is the new leading line: master now tracks the v2.0.0.0 trunk.
UPDATE, zero-deserialize in-place field patches, write-behind overwrites inside transactions, and a unified delete core.GROUP BY SUM; zero-allocation struct-row reads via ExecuteQueryStruct..scdb files are migrated transparently, with the original preserved as <file>.backup.BlockCompressionLevel, MetadataCompressionLevel: Fastest / Optimal / SmallestSize) and a CompressionThreshold.Compressed-flag bugs (PR #352).EncryptionPassword): random per-file data-encryption-key wrapped by PBKDF2-HMAC-SHA256 (OWASP-2024 defaults); raw EncryptionKey mode still supported.EncryptionMode = 2): registry, FSM and WAL encrypted.FsmSizePages, BlockRegistrySizePages, TableDirectorySizePages replace the hard-coded 4-page regions.n.n.n.n versions. NuGet normalizes the trailing zero (this release publishes as 2.0.0; assembly/file version is 2.0.0.0); future patches (2.0.0.1, 2.0.0.2, …) appear as 4-part versions on NuGet.dotnet pack verified..scdb databases are migrated automatically on first open (one-way; <file>.backup preserved).v1.9 maintenance: the 1.9.x line is preserved as the release/v1.9 branch (tag V1.9.9).
Full Changelog: V1.9.8...V1.9.9