Ultra-low-latency, persistent key-value storage for React Native and Expo. The core is written in Rust on top of scc (a lock-free concurrent hash map), and it reaches JavaScript through Nitro Modules, so a call from JS to Rust costs nanoseconds, not microseconds.
This project is also a statement of intent: bringing Rust closer to React Native. A Rust core behind Nitro Modules ships as an ordinary npm package — no toolchain for consumers, no compromise on performance — and this library is the proof that the pattern can go head-to-head with established C++ storage libraries.
The design goal is simple: every read is a RAM lookup, every write is durable, and the disk never sits on your hot path. Writes update the in-memory map synchronously and stream to a write-ahead log on a background thread; a hard kill can cost you the last few milliseconds of writes, but committed data is never corrupted.
- All reads from RAM — the persistent store reads exactly as fast as a pure in-memory one
- Durable by default — write-ahead log with group commits, atomic snapshot compaction, CRC-protected recovery
- Sync and async APIs — sync for the hot path,
*Asyncvariants on Nitro's thread pool for anything that must not block the JS thread - Batch operations —
setMany/getManycross the bridge once for a whole record set - Encryption at rest — opt-in ChaCha20-Poly1305 per instance, snapshot and WAL both encrypted
- TTL + eviction — per-key expiry with a background sweeper, optional
maxEntriescap - Native change events — listeners and hooks react to writes made through any handle of the same store
- React hooks —
useKVString,useKVNumber,useKVBoolean,useKVBuffer,useKVJSON - State-manager adapters — zustand persist, jotai
atomWithKV, redux-persist engine as subpath exports - Zero-config persistence — storage lands in the platform app-data directory (iOS: Application Support, Android:
filesDir) - Multiple independent stores — each
idgets its own file pair, WAL thread, and durability settings - iOS + Android, Expo dev builds + bare React Native
JS-visible latency vs react-native-mmkv v4, measured in the example app: iOS simulator, Release configuration, 100k iterations per case, listener-free instances on both sides, ~100 keys already resident in each store, median of three runs. Run it yourself with the in-app "Run benchmark again" button.
Two things worth knowing about these numbers. Small strings (≤ ~22 bytes) are stored inline with zero heap allocation. And the measurement uses warm stores: on a near-empty store MMKV's 64-byte set is faster (an mmap append is cheapest while the file is tiny), but once a store holds real data its writes settle around 550 ns while scc stays flat — the WAL write path does not degrade as the store grows. The Rust core itself (criterion, Apple Silicon): get 26 ns, set/overwrite 27 ns in-memory and 77 ns with the WAL attached.
npm install react-native-scc-storage react-native-nitro-modules{ "plugins": ["react-native-scc-storage"] }npx expo prebuild
npx expo run:ios
npx expo run:androidExpo Go is not supported (native code) — use a dev build.
cd ios && pod installPrebuilt Rust static libraries ship with the package. If they are missing (e.g. a source checkout), the build scripts compile them automatically — that path requires a Rust toolchain with the iOS/Android targets installed.
import { createKV } from 'react-native-scc-storage'
const kv = createKV() // persistent, id 'default'
// sync — the hot path
kv.set('user.name', 'Ada')
kv.set('user.score', 42.5)
kv.set('user.premium', true)
kv.setJSON('user.prefs', { theme: 'dark' })
kv.getString('user.name') // 'Ada'
kv.getNumber('user.score') // 42.5
kv.getJSON<{ theme: string }>('user.prefs') // { theme: 'dark' }
// async — same store, Nitro thread pool
await kv.setAsync('big.blob', someArrayBuffer)
const blob = await kv.getBufferAsync('big.blob')
await kv.flushAsync() // durability barrier
// batch — one bridge crossing
kv.setMany({ a: '1', b: '2', c: '3' })
kv.getMany(['a', 'b', 'missing']) // ['1', '2', undefined]Every id is an independent store with its own files (<id>.snap + <id>.wal), its own background writer, and its own settings. Opening the same id twice returns the same underlying store.
const settings = createKV({ id: 'settings' })
const vault = createKV({ id: 'vault', durability: 'strict' }) // fsync every commit
const cache = createKV({ id: 'cache' }) // relaxed (default): ~1s fsync
const ui = createKV({ id: 'ui', persistence: 'none' }) // pure in-memory, no filesOptions: id, path (override the storage directory), persistence: 'wal' | 'none', durability: 'relaxed' | 'strict', recreate (wipe on open), encryptionKey (see below).
const vault = createKV({ id: 'vault', encryptionKey: 'my-secret-passphrase' })Everything the instance writes to disk — snapshot and write-ahead log alike — is encrypted with ChaCha20-Poly1305; the 256-bit cipher key is derived from the passphrase with SHA-256. Opening an encrypted store with a wrong key (or without one) fails without touching the files, and opening a plaintext store with a key fails too, so a configuration mistake can never silently corrupt or rewrite data. Store the passphrase in the platform keystore (Keychain / Android Keystore) — the library deliberately does not manage key storage for you.
kv.set('session.token', token, { ttlMs: 15 * 60 * 1000 })
kv.setJSON('cache.profile', profile, { ttlMs: 60_000 })Expired keys read as missing immediately (get, contains, getAllKeys all agree), and a background sweeper physically reclaims them — also from disk — on the instance's WAL thread (sweep interval: 30 s). TTL persists across restarts: a key set with a 1-hour TTL is still gone after a kill + relaunch past its deadline.
Persistent instances accept a maxEntries cap at the native layer (exposed through OpenOptions in the Rust core): when the store outgrows it, the sweeper evicts expired keys first, then arbitrary live keys until it fits. Eviction order is unspecified (not LRU) — use it as a safety cap, not a cache policy.
import { useKVNumber } from 'react-native-scc-storage'
function Counter() {
const [count, setCount] = useKVNumber('counter')
return <Button title={`${count ?? 0}`} onPress={() => setCount((count ?? 0) + 1)} />
}Each hook returns [value, setValue]; calling setValue(undefined) deletes the key. Hooks re-render on any write to the key, including writes made through other KV objects opened with the same id.
The listener fires for every mutation of the underlying store, from any handle. key is null after clearAll ("everything changed"). Delivery is asynchronous on the JS thread.
const sub = kv.addOnValueChangedListener((key) => {
console.log(key === null ? 'store cleared' : `changed: ${key}`)
})
sub.remove()One package, three subpath exports. zustand and jotai are optional peer dependencies — install only what you use.
import { create } from 'zustand'
import { persist, createJSONStorage } from 'zustand/middleware'
import { sccStateStorage } from 'react-native-scc-storage/zustand'
const useStore = create(
persist((set) => ({ bears: 0 }), {
name: 'bears',
storage: createJSONStorage(() => sccStateStorage()),
})
)The storage is synchronous, so zustand hydrates without an async gap — no loading flicker, no onRehydrateStorage dance.
import { atomWithKV } from 'react-native-scc-storage/jotai'
const counterAtom = atomWithKV('counter', 0)Reads synchronously on init (getOnInit) and reacts to writes made outside jotai — including other KV handles — via the native change listener.
import { createSccStorage } from 'react-native-scc-storage/redux'
const persistedReducer = persistReducer(
{ key: 'root', storage: createSccStorage() },
rootReducer
)| sync | async | returns |
|---|---|---|
set(key, value) |
setAsync |
void — value: string | number | boolean | ArrayBuffer |
setJSON(key, value) |
setJSONAsync |
void |
setMany(entries) |
setManyAsync |
void — Record<string, string> |
getString(key) |
getStringAsync |
string | undefined |
getNumber(key) |
getNumberAsync |
number | undefined |
getBoolean(key) |
getBooleanAsync |
boolean | undefined |
getBuffer(key) |
getBufferAsync |
ArrayBuffer | undefined |
getJSON<T>(key) |
getJSONAsync |
T | undefined |
getMany(keys) |
getManyAsync |
(string | undefined)[] |
contains(key) |
containsAsync |
boolean |
delete(key) |
deleteAsync |
boolean |
getAllKeys() |
getAllKeysAsync |
string[] |
clearAll() |
clearAllAsync |
void |
flush() |
flushAsync |
void — blocks until fsynced |
size |
— | number |
close() |
— | void |
Reading a key that holds a different type returns undefined (matching react-native-mmkv). Numbers are IEEE-754 doubles, i.e. exactly JS number semantics.
Writes update the in-memory map synchronously, then stream to a write-ahead log on a dedicated background thread. The writer batches records into group commits (8 ms or 128 KiB, whichever comes first). With durability: 'relaxed' (default) the log is fsynced about once per second; with 'strict' every group commit is fsynced. flush() / flushAsync() is the explicit barrier: it returns only after everything written so far is on disk.
On restart the store recovers from snapshot + WAL replay. Every record carries a CRC32; a torn tail from a hard kill is truncated and recovery continues — committed data is never lost or corrupted. When the WAL outgrows max(4 MiB, 2 × snapshot size), the background thread compacts it into a snapshot written atomically (temp file + rename), so readers and writers never block on compaction.
TypeScript (KV class, hooks, adapters)
└─ Nitro Modules (JSI, sync calls, zero-copy where possible)
└─ C++ HybridObjects
└─ C FFI (cbindgen, panic-safe boundary)
└─ Rust core: scc::HashMap (lock-free reads) + WAL writer thread
The Rust core is an independent crate (crates/kv-core) with its own test suite: crash-recovery tests that truncate the WAL at every byte offset, multi-threaded stress tests racing writers against compaction, and criterion benchmarks. The C ABI layer (crates/kv-ffi) wraps every entry point in catch_unwind, so a Rust panic can never unwind across the language boundary.
npm install
npm run specs # tsc + nitrogen codegen
npm test # jest (adapters + KV against a mock native layer)
cargo test --workspace # Rust core + FFI suites
cargo bench -p kv-core # criterion benchmarks
npm run rust:build # cross-compile static libs for iOS + AndroidThe example app under example/ runs a full on-device self-test (sync/async round-trips, persistence across launches, cross-handle change events) and the MMKV comparison benchmark with live charts.
MIT