FastCollisionDetectionLib VS react-native-mmkv

If anyone wants to benchmark, source code here https://github.com/tugrul512bit/FastCollisionDetectionLib. It works only less than 32 overlapping on same volume(cell) its designed to work only with moderately colliding particles with or without teapot-in-stadium problem.

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