5 ms·

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

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

pritambarhate 10y ago
This seems quite interesting. Hope they chose MIT or Apache for license as said in the ReadMe.
- spb 10y ago
  MIT: https://github.com/rethinkdb/horizon/commit/79304a56fbcd57a65a534a0e1caa6164c3c5cb02 https://github.com/rethinkdb/horizon/commit/79304a56fbcd57a6...
guelo 10y ago
Horizon is only the "realtime db" portion of Firebase and it's only for Javascript, not Android or iOS. The mobile app realtime network connection tech is especially tricky to get right without draining a user's battery by doing things like constantly polling the backend. I have not seen anything from RethinkDB along those lines.
- hiphipjorge 10y ago
  > by doing things like constantly polling the backend RethinkDB doesn't require polling. It's like their #1 feature and differentiator from other non-sql databases.
  - deleted 10y ago
    [deleted]
  - EGreg 10y ago
    What do they do? We use websockets in our realtime platform.
    - coffeemug 10y ago
      The Horizon client uses websockets to connect to the Horizon server. The Horizon server uses RethinkDB's protocol[1] to connect to the database. [1] http://rethinkdb.com/docs/writing-drivers/ http://rethinkdb.com/docs/writing-drivers/
      - guelo 10y ago
        Websockets cannot be as efficient as native network management code.
        jkarneges 10y ago
        What does this even mean? WebSockets can be used natively. In fact the Firebase client uses WebSockets, same as Horizon.
        guelo 10y ago
        Sorry I was confused about terms, what I was thinking of was Javascript vs native. Native code can do more than a browser sandboxed client can.
- kuschku 10y ago
  > is especially tricky to get right without draining a user's battery by doing things like constantly polling the backend One simple solution is giving each state a defined name, and keeping a socket open from mobile. If the connection is restarted, each side can name their current state, and the delta can also be easily synced. Later on, changes can be directly transmitted via the socket. (I am working on something like that currently myself).
- zeeshanm 10y ago
  Horizon uses push architecture by default so there is no need to pool.
- deleted 10y ago
  [deleted]
- dmitriz 10y ago
  I presume you can still use it with any mobile App wrapped as native e.g. via React Native or Ionic.
JoshTriplett 10y ago
What about the new "Firebase Cloud Messaging", formerly GCM?
curiousGambler 10y ago
I was at ng-conf a couple weeks ago. Talking to the Firebase guy at their booth, he goes "You should talk to the RethinkDB guys, it's the same thing but open source." I got a kick out of it.

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

pritambarhate 10y ago

This seems quite interesting. Hope they chose MIT or Apache for license as said in the ReadMe.

spb 10y ago
MIT: https://github.com/rethinkdb/horizon/commit/79304a56fbcd57a65a534a0e1caa6164c3c5cb02 https://github.com/rethinkdb/horizon/commit/79304a56fbcd57a6...

guelo 10y ago

Horizon is only the "realtime db" portion of Firebase and it's only for Javascript, not Android or iOS. The mobile app realtime network connection tech is especially tricky to get right without draining a user's battery by doing things like constantly polling the backend. I have not seen anything from RethinkDB along those lines.

hiphipjorge 10y ago
> by doing things like constantly polling the backend RethinkDB doesn't require polling. It's like their #1 feature and differentiator from other non-sql databases.
- deleted 10y ago
  [deleted]
- EGreg 10y ago
  What do they do? We use websockets in our realtime platform.
  - coffeemug 10y ago
    The Horizon client uses websockets to connect to the Horizon server. The Horizon server uses RethinkDB's protocol[1] to connect to the database. [1] http://rethinkdb.com/docs/writing-drivers/ http://rethinkdb.com/docs/writing-drivers/
    - guelo 10y ago
      Websockets cannot be as efficient as native network management code.
      - jkarneges 10y ago
        What does this even mean? WebSockets can be used natively. In fact the Firebase client uses WebSockets, same as Horizon.
        guelo 10y ago
        Sorry I was confused about terms, what I was thinking of was Javascript vs native. Native code can do more than a browser sandboxed client can.
kuschku 10y ago
> is especially tricky to get right without draining a user's battery by doing things like constantly polling the backend One simple solution is giving each state a defined name, and keeping a socket open from mobile. If the connection is restarted, each side can name their current state, and the delta can also be easily synced. Later on, changes can be directly transmitted via the socket. (I am working on something like that currently myself).
zeeshanm 10y ago
Horizon uses push architecture by default so there is no need to pool.
deleted 10y ago
[deleted]
dmitriz 10y ago
I presume you can still use it with any mobile App wrapped as native e.g. via React Native or Ionic.

JoshTriplett 10y ago

What about the new "Firebase Cloud Messaging", formerly GCM?

curiousGambler 10y ago

I was at ng-conf a couple weeks ago. Talking to the Firebase guy at their booth, he goes "You should talk to the RethinkDB guys, it's the same thing but open source." I got a kick out of it.