关于react-native-mmkv在React Native旧架构下实现同步机制的技术咨询

Hey there! Awesome question—this trips up a lot of folks because most React Native libraries on the old architecture rely on the asynchronous bridge for JS-native communication. Let me walk you through how react-native-mmkv pulls off synchronous operations even in that legacy setup.

First, let's start with the core of MMKV itself: it's built on mmap (memory-mapped file) technology. Instead of doing slow, asynchronous disk I/O like many other storage libraries, MMKV maps the entire storage file directly into the app's memory. This means every read/write operation happens directly in memory—no waiting for disk operations to finish, so the underlying operations are inherently synchronous and lightning-fast (we're talking nanosecond-scale latency here).

Now, for the React Native old architecture part: normally, Native Modules communicate with JS via the asynchronous bridge, which queues messages and introduces overhead. But react-native-mmkv takes a different approach here. It implements synchronous Native Module methods specifically for the old architecture. Since MMKV's underlying operations are so fast, calling these synchronous methods from the JS thread doesn't block the UI or cause performance hiccups—something you'd never want to do with slower operations like network calls or large database queries.

To put it simply: the bridge is still present in the old architecture, but react-native-mmkv skips the async message queue for its operations. Instead, it lets JS directly invoke synchronous native methods that talk to the memory-mapped MMKV store. Since those native methods finish almost instantly, there's no risk of freezing the JS thread.

Just a quick heads-up: while this works perfectly for MMKV, you shouldn't copy this pattern with other libraries unless you're 100% sure their native operations are as low-latency as MMKV's. Slow synchronous calls on the old architecture can easily cause app jank.

备注：内容来源于stack exchange，提问作者Madhu Avinash