bad news from parse
bad news from parse
http://blog.parse.com/announcements/moving-on/
we used it a lot, just for temp storage between mobile app and customers local server....
kinvey is the natural alternative, but is more expansive.
any idea?
http://blog.parse.com/announcements/moving-on/
http://blog.parse.com/announcements/moving-on/
we used it a lot, just for temp storage between mobile app and customers local server....
kinvey is the natural alternative, but is more expansive.
any idea?
http://blog.parse.com/announcements/moving-on/
/sub
ReplyDeleteI would be interested to hear more about the "Host your own Parse Server" thing. Perhaps we find some other "Parse" service providers in the future?
ReplyDeleteIf you were only using them for data, with "low" volume (ie. less than a terabyte) hosting it in your own service on your own servers would probably be simpler, more secure and cheaper, let alone more future-proof.
ReplyDeleteReplicating the various advanced APIs, analytics, etc. is more involved, if only because they interface against moving targets, and services like Kinvey make a lot of sense. Same if you have terabytes of data, or millions of data-producing users across the world.
But for small scale guid/blob storage, all you really need is a high availability server/storage and some lines of code. Even having lots of data-consuming users can be handled by leveraging a CDN in many cases.
first step in TparseProvider component will be to add the api uURL as parameter ( Marco Cantù ,, maybe you are on time! ) so you can use your own server.
ReplyDeletei my case, i'll think only to have my mongodb db, maybe with mongolab service, or similar.
but user autoh and parameters are useful for us....
well , there's 1 year... let's think!
If this "host your own" feature happens, sure, we can allow for customization (and you have the source code, BTW). But if you used our BaaS architecture, migration to other providers should be fairly simple.
ReplyDeletekeep baas architecture is the target!
ReplyDeletefor standard purpose, migration to kinvey should be quite easy, there's some query syntax to change.
but i made some extension , creating some class reading other parse feature, like "config parameters" and so on, using rest call... sob!
Running your own node.js server may definitively do the trick. Worth considering, and a cheap approach.
ReplyDeleteYou may consider also setup your own server, using a mORMot back-end, to host your services and data - http://mormot.net allows to store not only your data, but also write your services in pascal, using interfaces. It would even allow to access a MongoDB storage via REST, containing your old data (Parse announcement state that you could have a MongoDB backup of the content).
Parse in, Parse out. Configure.IT is inviting Parse users
ReplyDeletehttps://plus.google.com/+ConfigureIt/posts/T6J1BuZZKSV
it not seems the right way ( at least for me) . database is mysql... but they are the first of a long list of offers :)
ReplyDelete