2 ms·

This is neat, but it seems like it's missing a few things. For one, how do you do migrations? Do I need to include every migration in my application bundle in p

This is neat, but it seems like it's missing a few things. For one, how do you do migrations? Do I need to include every migration in my application bundle in perpetuity, running them in the client on startup? There doesn't seem to be a mechanism to help with downloading, migrating, and reuploading data. That doesn't feel so nice. More pertinent, though, how do I ensure my users aren't abusing my service? If I allow folks to upload avatars for folks in their address book, how can I stop someone from running up my bill by uploading their MP3 collection? As far as I can tell, if everything is encrypted, I just have some very active users. Obviously there's some amount of tradeoff here, but it would seem like a necessary counterbalance is strong quota controls, which I don't see in the docs.

tasn 6y ago
Yeah, as I said in my main comment, there are still things that need to be done. One of them is strong quotas. We plan on having it in the near future (we are also running a service, EteSync, using Etebase) though I think it's not an issue that should prevent you from getting started. :) As for migrations: that's a tough one, and we indeed don't have an easy-to-use mechanism yet. I mentioned it in another comment: the API at the moment is powerful and used in production, but it's still missing some goodies to make the developer experience even better. As for including every migration in your application bundle: yeah, well until you consider an old version EOL. It's the same challenge Microsoft has with Office, and every app has with their local storage.