that is correct, you'll have to build the sync feature yourself. With that said, you'll gain on improved performance/scalability and no server management.
In terms of scalability, I have a policy that scaling should be considered only when it has to scale.
I wanted to release the app as quick as possible in order to check if it solves people's itch.
Besides, Inkdrop is for professionals in a niche market.
Looks like I still don't have to massively scale out.
From feature perspective, I really think PouchDB & CouchDB were a great choice for my app as it supports revisions so you can restore old revision, which is handy to support edit history. Changes feed is also awesome to support backup feature.
So, I'm totally happy with CouchDB and PouchDB with self-hosting.
Implementing data sync feature is complicated. I believe DynamoDB doesn't have such feature out of the box.
that is correct, you'll have to build the sync feature yourself. With that said, you'll gain on improved performance/scalability and no server management.
You are right.
In terms of scalability, I have a policy that scaling should be considered only when it has to scale.
I wanted to release the app as quick as possible in order to check if it solves people's itch.
Besides, Inkdrop is for professionals in a niche market.
Looks like I still don't have to massively scale out.
From feature perspective, I really think PouchDB & CouchDB were a great choice for my app as it supports revisions so you can restore old revision, which is handy to support edit history.
Changes feed is also awesome to support backup feature.
So, I'm totally happy with CouchDB and PouchDB with self-hosting.
it's an interesting database, I haven't considered using it since I'm so into the Amazon services world. Thanks for the explanation!