WatermelonDB VS rasgueadb

Storing the notes: For storing the notes, we will use the amazing WatermelonDB package which is a popular sqlite wrapper for react-native. Instead of using the default package we will use a fork of this that uses sqlcipher instead of the regular sqlite, allowing us to encrypt the database by passing a secret key.

Because most of the libraries I evaluated (RxDB, WatermelonDB) were entirely JS oriented, by design, none could provide a positive API surface in Native code.

never tried it but there is https://github.com/nozbe/WatermelonDB

As title says, is it a good option? There'll be like 60 webp images not some high quality. Or should I add some local db instead, something like: 1. https://github.com/ammarahm-ed/react-native-mmkv-storage 2. https://github.com/Nozbe/WatermelonDB

Watermelon DB.

Significantly improved performance (a lot of optimizations were done, and state management is more scalable by relying on an actual database)

Watermelondb it gives you an ORM, reactivity (when a records changes it cause UI re-render), and easy syncing with remote server, go with that if you don't know SQL that well.

More info here: https://github.com/Nozbe/WatermelonDB/issues/1254

Or WatermelonDb: https://nozbe.github.io/WatermelonDB/

I experimented with ObjectBox a bit, but I decided against using it because it isn't open source. The language wrappers are apache2 but the core library is only provided as a binary blob. I think this is bad because you can't inspect how it works, fix bugs, port it to new archs, integrate it fully into your build system, etc. Also, every cursor operation must call into their function entry points (as opposed to being inlined in your code for example).

Instead, I've been working on my own library which also uses LMDB and flatbuffers. It's C++ only and still a WIP, but in case anyone else is interested, it's here: https://github.com/hoytech/rasgueadb