deepstreamHub Launches, an Open Source Real-Time Server

| by Kevin Farnham Follow 0 Followers on Jul 21, 2016. Estimated reading time: 1 minute |

A note to our readers: You asked so we have developed a set of features that allow you to reduce the noise: you can get email and web notifications for topics you are interested in. Learn more about our new features.

German start-up deepstreamHub has launched, an open source, scalable, real-time server platform. The platform is designed for applications that require a network of device-resident nodes that communicate with cloud applications or with one another. Individual nodes can subscribe to topics and receive data whenever other clients publish to those topics. Nodes can also register functions that can be called by other nodes. The deepstreamHub platform is also available as a resource for additional services.

In a conversation with Saleha Riaz of Mobile World Live, deepstreamHub founders Yasser Fadl and Wolfram Hempel said that more than 10,000 developers are working with the deepstream technology. Hempel described deepstreamHub as providing:

a rich and open ecosystem of third party integrations that allow users to stream data from and to messengers like Slack, developer platforms such as GitHub, social networks, IoT endpoints, payment providers and open data sets.

Developers can install deepstream or download the code from GitHub. The software is primarily Javascript.

The Getting Started tutorial illustrates how to start a server and connect to it from a simple web page using the Javascript client.

The tutorial shows how to create a simple index.html page that consists of a single text field with Javascript that connects with the installed client. A deepstream record is integrated into the page and bound to the text field. The tutorial describes "records" as being "small bits of data that are synced across all connected clients."

The user then opens the index.html page in two separate browser windows (as depicted in the image above), and types some characters into the text field in one of the browser windows. The changed status of the text field is immediately communicated by the client to the installed server, which communicates the changes to the second browser via its client. As the animated GIF image at the top of the Getting Started page shows, the changes are communicated immediately, on a character-by-character basis.

The deepstream API Documentation is thorough. The Info page includes information about the community, performance testing, message protocol, and client behavior specifications.

Rate this Article

Adoption Stage

Hello stranger!

You need to Register an InfoQ account or or login to post comments. But there's so much more behind being registered.

Get the most out of the InfoQ experience.

Tell us what you think

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread
Community comments

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread


Login to InfoQ to interact with what matters most to you.

Recover your password...


Follow your favorite topics and editors

Quick overview of most important highlights in the industry and on the site.


More signal, less noise

Build your own feed by choosing topics you want to read about and editors you want to hear from.


Stay up-to-date

Set up your notifications and don't miss out on content that matters to you