Looks impressive, but as a Parse user I think that the selling point are the open-sourced SDKs for lots of platforms.
EDIT: this seems to be lacking a graphical administration panel as well.
Kinto – open-source alternative to Firebase and Parse
11–20 of 95 posts
Re: Kinto – open-source alternative to Firebase and Parse
#12Isn't one of the main benefits of something like Firebase or Parse that you don't have to run it? It's nice that Kinto packages the stack together and provides plug-and-play APIs, but there's quite a bit of expertise and overhead operating a backend stack in production.
Maybe, but there are others of us who don't use firebase because we can't outsource our datastore like that. It goes both ways.
Re: Kinto – open-source alternative to Firebase and Parse
#13Isn't one of the main benefits of something like Firebase or Parse that you don't have to run it? It's nice that Kinto packages the stack together and provides plug-and-play APIs, but there's quite a bit of expertise and overhead operating a backend stack in production.
In many industries (I.e. healthcare with HIPAA) you can't save your data in Firebase/Parse.
Re: Kinto – open-source alternative to Firebase and Parse
#14Would be nice if they included RethinkDB in comparison as well
Re: Kinto – open-source alternative to Firebase and Parse
#15Isn't one of the main benefits of something like Firebase or Parse that you don't have to run it? It's nice that Kinto packages the stack together and provides plug-and-play APIs, but there's quite a bit of expertise and overhead operating a backend stack in production.
In many industries (I.e. healthcare with HIPAA) you can't save your data in Firebase/Parse.
Parse is HIPAA certified.
Re: Kinto – open-source alternative to Firebase and Parse
#16I'm a big fan of services like Parse & Firebase so it's cool to see something open source and independent get released.
I've never made the jump to use Parse or Firebase in production though because inevitably I have to write some custom server code to do some integration. For example - payments with Stripe. Charges should only occur on your server (not on the client) but I've yet to see anyone allow you to configure a payment trigger in one of these services.
Re: Kinto – open-source alternative to Firebase and Parse
#17Looks impressive, but as a Parse user I think that the selling point are the open-sourced SDKs for lots of platforms. EDIT: this seems to be lacking a graphical administration panel as well.
I agree with you, but I think SDKs for at least Android and iOS will be available very soon.
Re: Kinto – open-source alternative to Firebase and Parse
#18It's not really an alternative to Firebase until you have change notification and a similar scaling model (i.e. scale by throwing money at it).
Re: Kinto – open-source alternative to Firebase and Parse
#19I'm a big fan of services like Parse & Firebase so it's cool to see something open source and independent get released. I've never made the jump to use Parse or Firebase in production though because inevitably I have to write some custom server code to do some integration. For example - payments with Stripe. Charges should only occur on your server (not on the client) but I've yet to see anyone allow you to configure…
We use parse with stripe. The client drives the transaction and then stripe hits your parse cloud function via webhook with the confirmation.
Re: Kinto – open-source alternative to Firebase and Parse
#20I'm not a big fan of offline storage for web apps. Any serious app will quickly exceed the localStorage limit which is only 5mb.
I would also question the decision to use HTTP for this purpose instead of WebSockets.