Live data from Hacker News

Kinto by Mozilla – An open-source Parse alternative

github.com

31–40 of 77 posts

Re: Kinto by Mozilla – An open-source Parse alternative

#33
post #23
post #20

Earlier quoted context omitted.

This is not a feature complete replacement AFAIK. No push , no cloud code , no webhooks , no admin panel , no analytics though I'm sure people will contribute to the project and add some of these features. EDIT: Hi folks, I was obviously talking about Parse, not Kinto. Kinto seems to have more features than Parse Server for now ! Looks like an awesome replacement.

There's an admin panel https://github.com/Kinto/kinto-admin Push: https://github.com/Kinto/kinto-webpush and https://github.com/leplatrem/cliquet-pusher What do you mean by "cloud code"? Anyway yeah, we're expecting help from the community to bring what's missing :)

I think the parent was talking about the open sourced parse code not being feature complete.

Re: Kinto by Mozilla – An open-source Parse alternative

#34
Realtime - Firebase, Meteor, GUN[0], PouchDB. People should NOT consider Kinto, RethinkDB, and Parse as realtime because you have to manually add that functionality yourself.

Permissions/Auth - Firebase, Parse. The way these two services do permissions is very different than everybody else (correct me if I am wrong). Therefore others are not comparable.

Graph - GUN. I think this is an important comparison for people to think about, all the other databases are essentially document stores. Graph data allows you to do key/value, relational, document oriented data, as well as have circular references.

[0] http://github.com/amark/gun Full disclosure: I'm the author.

Re: Kinto by Mozilla – An open-source Parse alternative

#37
post #15

At this point, Parse is open source, too. Why an open source clone if you can have the original?

My understanding was that Parse (the company) has open-sourced an API-compatible re-implementation of their product as an act of kindness towards everyone currently using their system.

I may be way off base here, but there is no indication that this open source release from Parse is in any way a derivative of their commercial product... at this point whichever reimplementation of the Parse API gains the most developer mind share will survive as the winner. (Of course, Parse the company has a lot of inertia behind their own.)

Re: Kinto by Mozilla – An open-source Parse alternative

#38
post #20
post #15

At this point, Parse is open source, too. Why an open source clone if you can have the original?

This is not a feature complete replacement AFAIK. No push , no cloud code , no webhooks , no admin panel , no analytics though I'm sure people will contribute to the project and add some of these features. EDIT: Hi folks, I was obviously talking about Parse, not Kinto. Kinto seems to have more features than Parse Server for now ! Looks like an awesome replacement.

You are correct that there is no push currently (we are exploring some ways to make it possible) and no admin panel (we are also exploring a lite admin panel), and no analytics (you should just use something like Mixpanel).

For cloud code, it's not true that parse-server doesn't support it - you can write cloud code directly in the node server.

For a full rundown on what's compatible, check out the migration guide: https://parse.com/docs/server/guide#migrating

The core functionality is there, and I highly recommend trying out the official Parse open source solution first, as it will be the easiest for most apps that want to migrate.

Re: Kinto by Mozilla – An open-source Parse alternative

#39

Here is a comparison table with Parse, Firebase, CouchDB and others for easy reference: http://kinto.readthedocs.org/en/latest/overview.html#compari...

Does it really compare to Parse tho? Like one of the amazing things about Parse was how easy it was for a nub to pick up. (I know from first hand exp)

Re: Kinto by Mozilla – An open-source Parse alternative

#40
CouchDB is so underrated in this space.

I get it: CouchDB was a very early (the first real?) document-based database, and it got some things wrong, or at least weird early on (e.g. map/reduce queries, a reduce step to the map/reduce query that is actually one-to-many (on purpose! there are concrete reasons in real life you want this!), etc.).

But they also got so much right:

   - The database is all HTTP, all the time. Connecting up your
     choice language takes about an hour.
   - Offline replication and database streaming, standardized at the
     protocol level, which allows you to use various combinations of
     CouchDB, Couchbase, Coucbase Lite, and PouchDB without interop
     problems. Plus, it means in the early part of an app (like the 0.X
     bit), I can trivially replicate the prod DB down when I'm trying
     to repro something.
   - You can store your HTTP assets right alongside the DB for 
     Firebase-like asset hosting. Throw it behind a caching service
     for prod if you want.
   - You can store full-blown files, which is great for lots of practical
     app these days.
   - Trivial replication. The scaling of CouchDB itself is honestly a
     bit crappy, but Couchbase has great scaling, and since they speak
     the same protocol, you can easily scale from CouchDB to Couchbase
     without missing a beat.
CouchDB is actually my favorite "I just wanna hack something" database for the above reasons. No, I have not and do not know if I'd seriously recommend using CouchDB 1.6 in prod for something you expected to grow huge, but it's a great "get it done" platform like Parse or Firebase, and you can really trivially move to Couchbase as you scale up if you need to.
Post reply on HN