You might also want to use API Caching, like caching HTTP requests etc. You should also consider synchronization with the server, specially when writing changes to data. Don't allow changes to data, if you do, you get into a big trouble. Couchbase Client, has a sync gateway that does this automatically for you. https://www.couchbase.com/products/mobile https://developer.couchbase.com/documentation/mobile/current/guides/sync-gateway/index.html

Thats why we examined the alternatives like Arangodb or Couchbase. We used Arangodb in production, but the problem is that, the TECH is not as mature and as stable as an old school giant like mysql or postgre. We hit stability issues from time to time, and we happen to report bugs. Sometimes my nightmare is that, I ask, what is the cost of trusting the tech? What are our options? 1- Rewrite the Service Model and migrate to another DBMS 2- Have a good Server Infra Team, and hunt down bugs as soon as possible and report them for fixation!

A Physician.

I've read online; the issues about OrientDB Were using ArangoDB for 10 months I've personally submitted at least 3 bugs, and other issues during this period The team is responsive, and they try their best to resolve the issues But there are still some bugs that they delay fixing them You should be reading the open issues to avoid these bugs Some of them that I can remember: 1- Do Not use "global" object in Foxx Services! You can FU** the whole DBMS 2- You Can't Have different databases with the same collection names and document keys, it causes DATA LOSS (e.g. DB A and B, both have a collection named "users", in both collections; exists a document with key 12, this causes the problem)