horizon

So the alternative options are: - pouchDB - https://github.com/pouchdb/pouchdb - RxDB - https://github.com/pubkey/rxdb - gunDB - https://github.com/amark/gun - horzion - https://github.com/rethinkdb/horizon - firebase - https://firebase.google.com/

There have been no commits to any of the branches in 18 days https://github.com/rethinkdb/rethinkdb/branches/all About the same for Horizon https://github.com/rethinkdb/horizon/branches/all The monthly Meetup was cancelled http://www.meetup.com/RethinkDB-SF-Meetup-Group/events/23340... Pretty much no activity on Github/Discuss/Twitter for two weeks, where they used to be very active.

The TL;DR: > It appears Horizon development slowed to a trickle. https://github.com/rethinkdb/horizon/graphs/contributors52 Are there any updates? > Slava @ Rethink here. Unfortunately I cannot comment yet (I really wish I could), but your intuition is right. We're working hard to be able to give a full account ASAP (matter of days). Please stay tuned. ... There is no legal action/litigation.

why not? There are lots of existing scaffolding having authorization setting up using passport https://github.com/jaredhanson/passport You don't even need to write code if you use https://github.com/rethinkdb/horizon, firebase, or similar services. For client side, you can reuse previously written code for authorization logic and just write user interface based on requirement. 40 hours are too much for such work

MIT: https://github.com/rethinkdb/horizon/commit/79304a56fbcd57a6...

Horizon[0] was announced yesterday; it's basically an open-source Firebase built on RethinkDB. [0]: https://github.com/rethinkdb/horizon

This is on our list : https://github.com/rethinkdb/horizon/issues/23 The big piece remaining that will help is write timestamps in the database, which we're going to try to land in RethinkDB 2.4. If we were controlling a traditional MVC frontend model and had control over the objects themselves, it would be easier to do optimistic updates. Since we're aiming to be compatible with a lot of frontend frameworks where immutability of the model is important, we have to carefully consider how to do it. That being said, it's super important, so it's near the top of our priorities

See also my issue about implementing the equivalent of Meteor's write fence: https://github.com/rethinkdb/horizon/issues/344

Hey @nileshtrivedi, We pushed a hotfix a few minutes after launch that resolved this issue [1] which you may be experiencing. You should try doing `npm update -g` if you're still on `horizon 1.0.0`. You can check with `hz version`. If this doesn't fix it for you, please open up an issue [2] and I will help you out. - [1] https://github.com/rethinkdb/horizon/issues/392 - [2] https://github.com/rethinkdb/horizon/issues/new

For apps that don't necessarily have the realtime requirement, Kinto [1] is another really cool open-source backend solution that focuses on the offline-first scenario. It's built by the Firefox Sync team and used in production at Mozilla. That said, at first glance there doesn't seem to be anything stopping anyone from building a caching layer on top of Horizon to enable offline-first functionality. Definitely going to be keeping an eye on this as well! EDIT: It looks like they are in fact considering offline-first support already [2]! [1] http://kinto.readthedocs.io/en/latest/overview.html [2] https://github.com/rethinkdb/horizon/issues/58

The current version of Horizon doesn't do optimistic updates, but it's on the roadmap. Check out https://github.com/rethinkdb/horizon/issues/23. This is relatively easy because RethinkDB itself has support for notifying the client via a feed when a particular update has landed (i.e. the RethinkDB client can correlate the write with a feed message). It just didn't make it into v1, but will happen soon.

There's currently no GraphQL support in Horizon, but it's on the roadmap. See https://github.com/rethinkdb/horizon/issues/125.