react-native-new-architecture VS react-native-mmkv

TurboModules: TurboModules are a new way of implementing native modules that use JSI instead of the bridge. TurboModules can reduce the overhead and latency of the native module calls, as well as provide a more consistent and type-safe interface for the JavaScript code. It is important to note that TurboModules are still experimental and not fully supported by all platforms and libraries

Finally, still about 0.72 RC1: Samuel Susla just made a post on performance benchmarking with some sweet new architecture 📈 measured on this RC. Check it out here 👉 https://github.com/reactwg/react-native-new-architecture/discussions/123

Also I can see on the GitHub a list of libraries that are migrated/migrating/plan to migrate here, https://github.com/reactwg/react-native-new-architecture/discussions/6. Is this really all the libraries that are compatible at this moment in time?

Detailed info - https://github.com/reactwg/react-native-new-architecture/discussions/105

[The discussion in the working group about libraries adopting the new architecture](https://github.com/reactwg/react-native-new-architecture/discussions/6) implies an urgency that not updated libraries will block the migration to the new architecture but I was wondering in what way exactly.

react-native-mmkv is a wrapper around MMKV that allows you to easily implement secure storage in your app. It is arguably the fastest key-value storage for React Native apps

Why do you need to access the db from the file system? Can you just use something like https://github.com/mrousavy/react-native-mmkv ?

By using libraries like Reanimated, React Native MMKV, and React Native Skia, you leverage the native thread. However, I know there are developers building amazing things who think outside the box. I'm always thrilled when I read engineering blogs from companies like Netflix, Meta, and Shopify. They create solutions beyond the limits.

mmkv is not really designed to be used for “heavy” writes, or often changing values. But more as e.g. NSUserDefaults. The storage keeps growing over time which may cause memory issues if used wrongly. Here’s a related github issue: https://github.com/mrousavy/react-native-mmkv/issues/440

Persistence - React Native MMKV (supports encryption natively and easily integrates with TanStack Query via persistQueryClient)

if you need to store something small and simple use whatever. if is complex and speed is important use something performant. realmDB, https://github.com/mrousavy/react-native-mmkv and others are good fit for the job.

Screw you all, I'll use MMKV as my Local DB: please do not, as explained here.

Try react native mmkv https://github.com/mrousavy/react-native-mmkv