Alternatives to Horizon logo

Alternatives to Horizon

Firebase, Socket.IO, Pusher, Google Cloud Pub/Sub, and SignalR are the most popular alternatives and competitors to Horizon.
15
50
+ 1
0

What is Horizon and what are its top alternatives?

Horizon provides a complete backend that makes it dramatically simpler to build, deploy, manage, and scale engaging JavaScript web and mobile apps. Horizon is extensible, integrates with the Node.js stack, and allows building modern, arbitrarily complex applications.
Horizon is a tool in the Realtime Backend / API category of a tech stack.
Horizon is an open source tool with 6.8K GitHub stars and 407 GitHub forks. Here’s a link to Horizon's open source repository on GitHub

Top Alternatives to Horizon

  • Firebase

    Firebase

    Firebase is a cloud service designed to power real-time, collaborative applications. Simply add the Firebase library to your application to gain access to a shared data structure; any changes you make to that data are automatically synchronized with the Firebase cloud and with other clients within milliseconds. ...

  • Socket.IO

    Socket.IO

    It enables real-time bidirectional event-based communication. It works on every platform, browser or device, focusing equally on reliability and speed. ...

  • Pusher

    Pusher

    Pusher is the category leader in delightful APIs for app developers building communication and collaboration features. ...

  • Google Cloud Pub/Sub

    Google Cloud Pub/Sub

    Cloud Pub/Sub is a fully-managed real-time messaging service that allows you to send and receive messages between independent applications. You can leverage Cloud Pub/Sub’s flexibility to decouple systems and components hosted on Google Cloud Platform or elsewhere on the Internet. ...

  • SignalR

    SignalR

    SignalR allows bi-directional communication between server and client. Servers can now push content to connected clients instantly as it becomes available. SignalR supports Web Sockets, and falls back to other compatible techniques for older browsers. SignalR includes APIs for connection management (for instance, connect and disconnect events), grouping connections, and authorization. ...

  • NATS

    NATS

    Unlike traditional enterprise messaging systems, NATS has an always-on dial tone that does whatever it takes to remain available. This forms a great base for building modern, reliable, and scalable cloud and distributed systems. ...

  • PubNub

    PubNub

    PubNub makes it easy for you to add real-time capabilities to your apps, without worrying about the infrastructure. Build apps that allow your users to engage in real-time across mobile, browser, desktop and server. ...

  • WCF

    WCF

    It is a framework for building service-oriented applications. Using this, you can send data as asynchronous messages from one service endpoint to another. A service endpoint can be part of a continuously available service hosted by IIS, or it can be a service hosted in an application. ...

Horizon alternatives & related posts

Firebase logo

Firebase

26.3K
22K
1.9K
The Realtime App Platform
26.3K
22K
+ 1
1.9K
PROS OF FIREBASE
  • 361
    Realtime backend made easy
  • 264
    Fast and responsive
  • 234
    Easy setup
  • 207
    Real-time
  • 186
    JSON
  • 127
    Free
  • 121
    Backed by google
  • 81
    Angular adaptor
  • 63
    Reliable
  • 36
    Great customer support
  • 26
    Great documentation
  • 23
    Real-time synchronization
  • 20
    Mobile friendly
  • 17
    Rapid prototyping
  • 12
    Great security
  • 11
    Automatic scaling
  • 10
    Freakingly awesome
  • 8
    Chat
  • 8
    Angularfire is an amazing addition!
  • 8
    Super fast development
  • 6
    Awesome next-gen backend
  • 6
    Ios adaptor
  • 5
    Built in user auth/oauth
  • 5
    Firebase hosting
  • 4
    Speed of light
  • 4
    Very easy to use
  • 3
    It's made development super fast
  • 3
    Great
  • 3
    Brilliant for startups
  • 2
    Great all-round functionality
  • 2
    Low battery consumption
  • 2
    I can quickly create static web apps with no backend
  • 2
    The concurrent updates create a great experience
  • 2
    JS Offline and Sync suport
  • 1
    Faster workflow
  • 1
    Large
  • 1
    Serverless
  • 1
    .net
  • 1
    Free SSL
  • 1
    Good Free Limits
  • 1
    Push notification
  • 1
    Easy to use
  • 1
    Easy Reactjs integration
CONS OF FIREBASE
  • 28
    Can become expensive
  • 15
    Scalability is not infinite
  • 14
    No open source, you depend on external company
  • 9
    Not Flexible Enough
  • 5
    Cant filter queries
  • 3
    Very unstable server
  • 2
    Too many errors
  • 2
    No Relational Data

related Firebase posts

Stephen Gheysens
Senior Solutions Engineer at Twilio · | 14 upvotes · 257.9K views

Hi Otensia! I'd definitely recommend using the skills you've already got and building with JavaScript is a smart way to go these days. Most platform services have JavaScript/Node SDKs or NPM packages, many serverless platforms support Node in case you need to write any backend logic, and JavaScript is incredibly popular - meaning it will be easy to hire for, should you ever need to.

My advice would be "don't reinvent the wheel". If you already have a skill set that will work well to solve the problem at hand, and you don't need it for any other projects, don't spend the time jumping into a new language. If you're looking for an excuse to learn something new, it would be better to invest that time in learning a new platform/tool that compliments your knowledge of JavaScript. For this project, I might recommend using Netlify, Vercel, or Google Firebase to quickly and easily deploy your web app. If you need to add user authentication, there are great examples out there for Firebase Authentication, Auth0, or even Magic (a newcomer on the Auth scene, but very user friendly). All of these services work very well with a JavaScript-based application.

See more
Tassanai Singprom

This is my stack in Application & Data

JavaScript PHP HTML5 jQuery Redis Amazon EC2 Ubuntu Sass Vue.js Firebase Laravel Lumen Amazon RDS GraphQL MariaDB

My Utilities Tools

Google Analytics Postman Elasticsearch

My Devops Tools

Git GitHub GitLab npm Visual Studio Code Kibana Sentry BrowserStack

My Business Tools

Slack

See more
Socket.IO logo

Socket.IO

8.6K
7.1K
773
Realtime application framework (Node.JS server)
8.6K
7.1K
+ 1
773
PROS OF SOCKET.IO
  • 213
    Real-time
  • 142
    Event-based communication
  • 141
    Node.js
  • 102
    Open source
  • 101
    WebSockets
  • 26
    Binary streaming
  • 22
    No internet dependency
  • 9
    Fallback to polling if WebSockets not supported
  • 8
    Large community
  • 5
    Ease of access and setup
  • 4
    Push notification
CONS OF SOCKET.IO
  • 11
    Bad documentation
  • 4
    Githubs that complement it are mostly deprecated
  • 3
    Doesn't work on React Native
  • 2
    Websocket Errors
  • 2
    Small community

related Socket.IO posts

across_the_grid
Full-stack web developer · | 10 upvotes · 332.3K views
Shared insights
on
Socket.IO
Node.js
ExpressJS

I use Socket.IO because the application has 2 frontend clients, which need to communicate in real-time. The backend-server handles the communication between these two clients via websockets. Socket.io is very easy to set up in Node.js and ExpressJS.

In the research project, the 1st client shows panoramic videos in a so called cave system (it is the VR setup of our research lab, which consists of three big screens, which are specially arranged, so the user experience the videos more immersive), the 2nd client controls the videos/locations of the 1st client.

See more

We are starting to work on a web-based platform aiming to connect artists (clients) and professional freelancers (service providers). In-app, timeline-based, real-time communication between users (& storing it), file transfers, and push notifications are essential core features. We are considering using Node.js, ExpressJS, React, MongoDB stack with Socket.IO & Apollo, or maybe using Real-Time Database and functionalities of Firebase.

See more
Pusher logo

Pusher

515
1.2K
230
Hosted APIs to build realtime apps with less code
515
1.2K
+ 1
230
PROS OF PUSHER
  • 51
    An easy way to give customers realtime features
  • 40
    Websockets
  • 35
    Simple
  • 27
    Easy to get started with
  • 25
    Free plan
  • 12
    Heroku Add-on
  • 11
    Easy and fast to configure and to understand
  • 9
    JSON
  • 6
    Azure Add-on
  • 5
    Support
  • 5
    Happy
  • 4
    Push notification
CONS OF PUSHER
  • 9
    Costly
  • 0
    Aa

related Pusher posts

Which messaging service (Pusher vs. PubNub vs. Google Cloud Pub/Sub) to use for IoT?

See more
Kirill Shirinkin
Cloud and DevOps Consultant at mkdev · | 3 upvotes · 228K views
Shared insights
on
Mattermost
Pusher
Twilio
at

Recently we finished long research on chat tool for our students and mentors. In the end we picked Mattermost Team Edition as the cheapest and most feature complete option. We did consider building everything from scratch and use something like Pusher or Twilio on a backend, but then we would have to implement all the desktop and mobile clients and all the features oursevles. Mattermost gave us flexible API, lots of built in or easy to install integrations and future-proof feature set. We are still integrating it with our main platform but so far the team, existing mentors and students are very happy.

See more
Google Cloud Pub/Sub logo

Google Cloud Pub/Sub

395
329
6
Global service for real-time and reliable messaging and streaming data
395
329
+ 1
6
PROS OF GOOGLE CLOUD PUB/SUB
  • 5
    Easy to set-up and start with
  • 1
    1
CONS OF GOOGLE CLOUD PUB/SUB
  • 2
    Need integration with stackdriver for monitoring

related Google Cloud Pub/Sub posts

Which messaging service (Pusher vs. PubNub vs. Google Cloud Pub/Sub) to use for IoT?

See more
SignalR logo

SignalR

386
951
106
A new library for ASP.NET developers that makes developing real-time web functionality easy.
386
951
+ 1
106
PROS OF SIGNALR
  • 24
    Supports .NET server
  • 16
    Real-time
  • 13
    Free
  • 13
    Fallback to SSE, forever frame, long polling
  • 12
    WebSockets
  • 7
    Simple
  • 7
    JSON
  • 6
    Open source
  • 4
    Ease of use
  • 4
    Cool
CONS OF SIGNALR
  • 2
    Expertise hard to get
  • 1
    Big differences between ASP.NET and Core versions
  • 1
    Requires jQuery
  • 1
    Weak iOS and Android support

related SignalR posts

Shared insights
on
gRPC
SignalR
.NET

We need to interact from several different Web applications (remote) to a client-side application (.exe in .NET Framework, Windows.Console under our controlled environment). From the web applications, we need to send and receive data and invoke methods to client-side .exe on javascript events like users onclick. SignalR is one of the .Net alternatives to do that, but it adds overhead for what we need. Is it better to add SignalR at both client-side application and remote web application, or use gRPC as it sounds lightest and is multilingual?

SignalR or gRPC are always sending and receiving data on the client-side (from browser to .exe and back to browser). And web application is used for graphical visualization of data to the user. There is no need for local .exe to send or interact with remote web API. Which architecture or framework do you suggest to use in this case?

See more
NATS logo

NATS

229
342
51
Lightweight publish-subscribe & distributed queueing messaging system
229
342
+ 1
51
PROS OF NATS
  • 20
    Fastest pub-sub system out there
  • 14
    Rock solid
  • 10
    Easy to grasp
  • 3
    Light-weight
  • 3
    Easy, Fast, Secure
  • 1
    Robust Security Model
CONS OF NATS
  • 1
    Persistence with Jetstream supported
  • 1
    No Order
  • 1
    No Persistence

related NATS posts

PubNub logo

PubNub

176
387
231
Build real-time apps quickly and scale them globally.
176
387
+ 1
231
PROS OF PUBNUB
  • 34
    Massively scalable & easy to use
  • 24
    Easy setup
  • 19
    Great support
  • 19
    Reliable
  • 14
    Flexible to integrate to custom applications
  • 13
    High-Performance
  • 12
    Sockets at Scale
  • 12
    99.999% availability guarantees
  • 12
    Multiplexing
  • 11
    High-Reliability
  • 7
    Scalability
  • 5
    High-Availability
  • 5
    70+ SDKs
  • 4
    Azure Add-on
  • 4
    Security
  • 3
    Presence
  • 3
    Heroku Add-on
  • 3
    Flexible
  • 3
    Easy to setup
  • 2
    Data Sync
  • 2
    AngularJS Adapter
  • 2
    PhoneGap Plugin
  • 2
    Server-Side Cache
  • 2
    Free Plan
  • 2
    Support
  • 2
    Analytics
  • 2
    Data Streams
  • 1
    Easy setup and very reliable
  • 1
    Real time and easy to use.
  • 1
    High cost, going up more in Summer '15
  • 1
    Cool
  • 1
    CTO stephen also is A++++++
  • 1
    Angular 2+ integration
  • 1
    Documentation, easy to use, great people/service
  • 1
    Easy integration with iOS apps
CONS OF PUBNUB
  • 1
    Costly

related PubNub posts

Which messaging service (Pusher vs. PubNub vs. Google Cloud Pub/Sub) to use for IoT?

See more
Shared insights
on
PubNub
Socket.IO

I am trying to replace Socket.IO with PubNub. Provide the way to do it.

See more
WCF logo

WCF

102
78
2
A runtime and a set of APIs for building connected, service-oriented applications
102
78
+ 1
2
PROS OF WCF
  • 2
    Classes
CONS OF WCF
    Be the first to leave a con

    related WCF posts