Current limitations

Horizon is rapidly evolving

• Some APIs and processes may (or will!) change in future releases.
• While a plug-in architecture is planned, it’s not here yet.
• Integrating Horizon with existing code is possible, but it’s still a work in progress. (See Embedding Horizon for more details.)
• There Will Be Bugs.

Currently, Horizon is well-suited for a simple to moderately complex front-end application. It’s possible to build a new Node app with Horizon, but it may be something of an adventure. Porting an existing Node application to Horizon may be difficult or even impossible. All of this will change in the future!

Requirements

Horizon should be compatible with most popular browsers, although it hasn’t been extensively tested with older versions. If you expect to run Horizon on browsers that do not support JavaScript ES6 promises, you will need to supply a polyfill to support them, such as es6-promise.

Currently, Horizon has issues with Mobile Safari. This will be addressed in an upcoming release.

There may be issues with Internet Explorer (see issue #566).

The Horizon server requires Node.js version 4.4 or higher, and the corresponding version of npm.

Setting up a Horizon server under Windows has not been extensively tested.

Limitations

• Horizon operations are non-atomic (even with single documents).
• User records for “anonymous” users need to be removed from the users collection manually after their JSON Web Tokens expire.
• The Horizon client cannot automatically reconnect to the Horizon server if the connection is lost.
• If the client manually reconnects to the server, active subscriptions will not automatically resume. They must be set up again by the client application.
• The only realtime access provided to the underlying RethinkDB database is through changefeeds.

Planned features

• GraphQL support (see issue #125)
• Pagination (see issue #31)
• Local user/password authentication (see issue #176)
• Reconnection logic (see issue #9)