I'm sure you've all heard Dropbox's news that they will be deprecating the Datastore API. I'm curious to know what everyone is going to move over to.
I originally chose the Datastore API for a few reasons:
I am currently considering a few other options, but I'd love to hear what you all are looking to do.
Firebase - firebase.com - This seems to be the most similar to the Datastore API so far. Developers claim it performs really well with large datasets. The downside is that it costs money for more concurrent connections (but the prices are reasonable).
Couchbase - couchbase.com - This is open source and seems pretty good. The downside is having to get your own server environment up and running.
Helios - helios.io - This seems to provide a lot of flexibility, but you have to do some of your own back-end setup, and it doesn't seem to provide an object-base sync interface. Instead, you have to use Core Data and its REST API.
Parse - parse.com - There is a lot to like about this option, and it can handle large datasets, but doing basic database operations like importing data and summing the numbers in a column is surprisingly difficult (for me, at least).
Anyone else found an alternative they like?
Good luck with your BaaS migration. :/
A word on Parse. I initially developed this app with a Parse interface. However, as I started to use it, I realized I could see (and change) all user data. That just isn't right, Maybe I implemented it incorrectly. I'd be interested in others' experiences.
My use case would be fine with switching to files, but the notifications are too noisy. I use the Dropbox API with a writing app, and it autosaves as you type. With the Datastore API, this wouldn't trigger notifications, but when updating files, there's a notification every time (unless the user disables all notifications).
Does anyone know of a way to disable (some) notifications when using the Core API?
Here is the results of my own experiments.
Links to persistence in Firebase (iOS, then Android).
Thanks for that rundown, Caram. I had looked at Cognito but wondered about its future since I don't know a single developer using it.
Since Dropbox's news about deprecating the Datastore API, I have been working with Parse. It requires a bit of a shift in how you think about storing data since it's much more about querying the cloud than it is storing data locally, but so far I am really liking it. I used to always want my data on the device, but this makes make my app slower. Doing lots of queries and intensive calculations on the device is doable, but using Cloud Code on Parse seems like a more reasonable way to handle such things.
Parse is unique in that it has a huge following and tremendous financial support from Facebook, so I see it being around for a long time and only getting better. I also like that I can see my users' data (to reference David D.'s comment) because it makes troubleshooting custom support issues MUCH easier. There's no way to see a user's data when using the Dropbox Datastore unless you log in with their Dropbox account.
The way we work is changing. Share and discover new ways to work smarter with Dropbox in our community.Sound good? Let's get started.
For more info on available support options, see this article.
If you found the answer to your question, please 'like' the post to say thanks to the user!