8DB | 19.99 million key-value reads/sec. Redis did 3.09 million.
Explore the measured path, comparison and conditions.
Explore the models / 8DB
Key-value
A direct route to the record you need.
Use keyed access for familiar application state, then connect that state to the other models your question needs.
Read · write · resolve
Model / Key-valueConceptual diagram
Start with the operations
your question needs.
- Point and range reads over stored keys
- Updates and typed operational records
- Filtering, sorting and projections on the relevant record path
Documented product scope, reviewed 17 September 2026. The underlying build and deployment must be qualified for your application.
A GET result measures a retrieval path. It does not establish durable write throughput, a complete graph query or the cost of a protected application response.
Connected native models
Keep the next question within reach.
The opportunity beyond a standalone lookup is continuity: retrieve an asset, follow its inspection relationships and bring back the supporting observations without treating each representation as an unrelated source of truth.
Follow the relationship to a better answer.
Connect · traverse · follow
Explore model ↗Keep the meaning in every observation.
Observe · window · analyze
Explore model ↗Keep the source behind the answer.
Structure · search · trace
Explore model ↗These connections show the models involved in the application design. Compare the supported combination and full workflow with a realistic alternative.
Input → usable value / interactive design example
Prepare an equipment service decision
Receive an asset identifier and current observation
Keys resolve to values. A direct lookup is a starting point for a wider application workflow.
Next: Resolve the record
Conceptual application workflow. Qualify the supported operations, external tools, protection and persistence for the complete path. These diagrams are explanatory, not measured results.
Read the complete workflow and comparison scope
- Receive an asset identifier and current observation
- Resolve the operational record with a key lookup
- Follow component and inspection relationships
- Retrieve the relevant readings and source report
- Return a service view with its supporting evidence
A separate cache, operational database and evidence search service can require identity mappings and freshness checks. Compare 8DB with the simplest alternative that actually meets the job, including a single integrated system where appropriate.
Compare a realistic alternative.
Redis provides several data types, so the alternative is broader than a bare key-value cache. Compare both the fast path and the rest of the application’s work.
Redis data typesCompare equivalent outputs and required guarantees, including the simplest single-product alternative where one exists. A specialist may remain the better fit when its operators, ecosystem or operational maturity are decisive. Combining native models becomes valuable when your actual question crosses them.
Modality performance / Evidence reviewed 18 September 2026
19.99 million key-value reads per second.
million operations / second Higher is better · linear scale from zero
8DB19.99
32-vCPU AMD · batch 128
Redis3.087
Same host · pipeline 128
Dragonfly6.43
External 64-vCPU reference
Different payload, workload, client and selection contracts. 8DB used an in-memory path; original-trial and correctness reconciliation remain open. These are reported configurations, not a matched speedup or current-product ranking.
Read the results, comparison and methods →01Payload & batch size
02Request p95 / p99
03Durable write completion
Include memory, storage, energy and hardware writes
Record build-time and serving memory separately, original and derived stored bytes, measured joules per completed job, and physical writes including indexing, compaction and recovery. A smaller representation does not by itself prove lower energy or longer device life.
Match correctness, freshness, durability and protection across alternatives. Encryption, authorization, adapters, network setup and output delivery belong in the complete-job comparison wherever required. No universal zero-overhead claim follows from these results.
Choose the path that fits your deployment.
Verify the supported API/SDK, data format, persistence and indexing behaviour for the release you plan to use. Match the operation-by-modality protection profile and device qualification to the workload.
Related articles
Take the next step into the thinking.
Show Your Work: Provenance as a Query, Not a Forensic Reconstruction
Explore the ideas and implementation context behind this capability.
One Sealed Store for Every Shape of Data, and It Works With the Network Gone
Explore the ideas and implementation context behind this capability.
Reference / Reviewed 17 September 2026
Readable, shareable and traceable.
This reference explains 8DB’s public modality description with an explicit workload and selection criteria. It is a documentary review, not fresh execution of every operator or platform.
Public sources: 8DB modality scope; Redis data types; the related articles above. Internal source leads and outstanding release checks remain in the editorial record.
Download this referenceEvaluate the question
your application needs to answer.
Bring the data shapes, input state, expected output and the systems you use today. Define a comparison around that complete job.
Discuss your workload