Both firebase and appwrite are amazing platforms. I use firebase extensively at work, it works great and it scales.
The main problem with firebase is that you can't self host it, this means you can't easily test or replicate environments.
The emulators are limited: indexes are not enforced, copying the production database (no more than 50k documents) to my macbook pro crashes the emulator.
Also the DSL used to define security rules is not flexible enough. I've seen developers skip defining rules because they don't get it to work.
Appwrite is great and you can self host it, but it introduces concepts/APIs to query data and secure it that you have to learn. They also try to solve the problem for all platforms and languages.
JSDB tries to extremely simplify things and just use plain javascript for everything.
You should use JSDB if you love javascript.
That being said, firebase & appwrite are both production ready and JSDB is not there (yet!!)
jpcapdevila|3 years ago
The main problem with firebase is that you can't self host it, this means you can't easily test or replicate environments.
The emulators are limited: indexes are not enforced, copying the production database (no more than 50k documents) to my macbook pro crashes the emulator.
Also the DSL used to define security rules is not flexible enough. I've seen developers skip defining rules because they don't get it to work.
Appwrite is great and you can self host it, but it introduces concepts/APIs to query data and secure it that you have to learn. They also try to solve the problem for all platforms and languages.
JSDB tries to extremely simplify things and just use plain javascript for everything.
You should use JSDB if you love javascript.
That being said, firebase & appwrite are both production ready and JSDB is not there (yet!!)