Deepstream.io – Open Realtime Server

https://deepstream.io/#1.0

by wolframhempel • 10 years ago

166 67 10 years ago

deepstream.io

120bits• 10 years ago

Page Not Found. When I clicked on Getting started

https://deepstream.io/core/getting-started-quickstart/

Edit: Clicked on tutorials and then Getting started.

wolframhempel18• 10 years ago

oops, thanks so much, fixed it

MasterScrat3• 10 years ago

From a quick look at it it looks like a self-hosted Firebase.

Would that be a good approximation?

wolframhempel18• 10 years ago

yup, that's not too far off. It also gives you Pub/Sub and Request/Response though. Also Firebase uses one huge data-structure for data-sync whereas deepstream breaks data down into smaller objects called "records" with individual lifecycles

duncanawoods• 10 years ago

Huh. I visited your site and reading the tag line "a fast, secure and scalable websocket & tcp server", I assumed it was just a socket server and had no idea it was actually a data-store.

lpinca2• 10 years ago

I'm confused. 1.1 has been released 13 days ago https://github.com/deepstreamIO/deepstream.io/releases/tag/v...

wolframhempel18• 10 years ago

yes, but we wanted to give it an initial test phase before announcing it to make sure we didn't miss anything major

andrewwhartion• 10 years ago

Isn't that what a release candidate is for?

lpinca2• 10 years ago

I'm still confused. You are announcing 1.0 but the actual version is 1.1

stemuk8• 10 years ago

Are there any plans for an iOS/Swift client? So far it seems only js and Java clients are available...

wolframhempel18• 10 years ago

Yup, we're in the process of finalizing it. There's a related issue at https://github.com/deepstreamIO/deepstream.io/issues/68 with links to the beta artefacts.

stemuk8• 10 years ago

Nice, really appreciate the progress here! However, is there any reason the artifacts aren't on github? It may be more convenient when it comes to issues/changelogs etc.

aw3c2• 10 years ago

Can't read the text, please review the contrast part of https://www.w3.org/TR/WCAG20/

stemuk8• 10 years ago

This might help you out for now (if you are using Firefox): https://support.mozilla.org/en-US/kb/accessibility-features-...

asadlionpk3• 10 years ago

This is great! I wish somebody would write a Firebase API compatible wrapper around this so escaping Firebase lock-in would be possible without altering code.

I might start it myself when I find some time.

cheriot2• 10 years ago

Or even just integration testing Firebase without hitting a remote service!

asadlionpk3• 10 years ago

that might be overkill. Here is a better solution: https://github.com/urish/firebase-server

dschiptsov• 10 years ago

Realtime? In nodejs?

It must be a webscale realtime, or at least reactive realtime..

hackerboos• 10 years ago

If you're willing to put the work in to load balance then it can probably scale quite well.

I'm always baffled why people choose JS over Erlang/Elixir which is designed to do this and comes with the tools/libs required to scale.

elcct• 10 years ago

Exactly word "probably" is a deal breaker in this case. I am also curious how someone was thinking JS will be a good idea for such project. But hey, there are people building cars out of plastic bottles...

akanet3• 10 years ago

Do you provide a version of Firebase's onDisconnect? https://firebase.google.com/docs/reference/js/firebase.datab...

It's very hard to correctly manage distributed state without a guarantee similar to this.

wolframhempel18• 10 years ago

Yes, there are granular connection states and associated events. Messages are queued during connection loss. Please find more information here.

https://deepstream.io/docs/client-js/client/#connectionstate...

https://deepstream.io/docs/common/constants/#connection-stat...

akanet3• 10 years ago

Sorry, I should have been clearer. I don't mean "does Deepstream tell the user when it's disconnected", I mean:

Does the Deepstream client have a facility (like Firebase) to instruct the remote server to perform an action in the event the client disconnects in the future and the client is unable to get any further message to the server?

asadlionpk3• 10 years ago

Since this is not built-in, it may be possible to make with deepstream's onClientDisconnect.

https://github.com/deepstreamIO/deepstream.io/issues/191

Also they seem to be working on 'presence'. https://github.com/deepstreamIO/deepstream.io/issues/118

kabes• 10 years ago

I really like that the documentation is quite honest and unbiased. Like with the integrations: https://deepstream.io/tutorials/integrations it always mentions downsides next to the upsides.

benjaminjt2• 10 years ago

This is a really good point actually. I particularly liked the overview of other realtime libraries[1] for the honesty factor, and it really helped me understand how it relates to more familiar frameworks too.

[1] https://deepstream.io/blog/realtime-framework-overview/

oakesm92• 10 years ago

How does this compare to something like ShareDB (https://github.com/share/sharedb)? It seems on the face of it that the data part of it is pretty similar (albeit Deepstream is more fully featured with auth etc.), however, there is no mention of how Deepstream handles conflict resolution if two clients are modifying the state.

Internally ShareDB uses Operational Transformation with special operations which are designed for use in JSON documents.

Does anyone know how this works in Deepstream?

wolframhempel18• 10 years ago

There's a choice of merge algorithms as well as the ability to hook in your own.

https://deepstream.io/tutorials/core/handling-data-conflicts...

oakesm92• 10 years ago

Thanks! I hadn't found that before.

Sounds like having those merge algorithms/hooks and splitting up the document into multiple "records" might actually be enough for my use case.

reactor4• 10 years ago

Genuine question, how does this different from https://github.com/centrifugal/centrifugo ?

wolframhempel18• 10 years ago

I'm afraid I don't know too much about centrifugo, but it looks like a pub-sub server you can connect to Redis. deepstream on the other hand provides datasync (stateful, persistent JSON objects you can subscribe and listen to), request-response and pubsub in a scalable way with granular permissions and authentication strategies and an ecosystem of connectors that make it work with different databases, caches and message buses.

reactor4• 10 years ago

Thanks, any plan for the android client?

phelm• 10 years ago

How does this compare to RethinkDB / Horizon ?

wolframhempel18• 10 years ago

Please find a detailed answer here:

https://deepstream.io/tutorials/integrations/db-rethinkdb/

marknadal2• 10 years ago

Wow, deepstream looks really good (and I'm a competitor, http://gun.js.org/ ). Your guy's product seems to have significantly matured over the last year. I'm very impressed! Up for chatting? mark AT gunDB DOT io (I still like your guys old website better though with the server/client graphic animation).

wolframhempel18• 10 years ago

Ooh, thanks so much. Just heading out for the inevitable "we've made the frontpage drink", but let's get in touch tomorrow. The diagram is still there, but buried in https://deepstream.io/tutorials/core/cluster-messaging/

marknadal2• 10 years ago

Yeah that one! I love that graphic! Your profile doesn't have your email address in it, so you'll have to ping me. Tomorrow sounds good. Congrats on the launch!

makkesk8• 10 years ago

I like it but coming from socket.io I have a hard time with it. For instance, Where/how would I put my server logic? The "Node API" as its called isn't really helpful or not documented enough. But then again, I could have misunderstood what deepstream is all about or how you are supposed to be using it.

wolframhempel18• 10 years ago

It's a different beast from socket.io :-) your server logic is just another client, written in java or node. There's a lot of functionality that let's you listen in on what clients request etc. Please find more details at https://deepstream.io/tutorials/core/active-data-providers/

partycoder2• 10 years ago

While it looks interesting, I honestly don't feel like building a system like this on top of node. Not because of the library itself, which seems properly implemented (hard to see libraries using proper formatting and JSDoc these days).

node is a simple, friendly technology, until you to profile it. Then it's not so friendly. With a realtime system you require a great deal of profiling and quite honestly the tooling is not there.

"Oh but what about Flamegraphs and DTrace?"... it is nothing compared to what you have in Java. And node tooling is better on obscure operating systems like IllumOS.

If I had to implement a system like this I would opt for Scala + Akka, or Elixir/Erlang. If it's for simplicity/budget reasons, try PubNub.

dragonne• 10 years ago

What tools do you use to profile a Scala + Akka service? IME they are quite opaque to traditional Java tools like VisualVM. What am I missing?

partycoder2• 10 years ago

Scala can be profiled with VisualVM.

You can monitor Akka with kamon.io, or using the tool offered by the authors.

samblr• 10 years ago

Could you please shed some light on concurrent connections benchmarks ? Im looking for a scalable solution - I am trying out socket.io and I read from others there are some performance issues as it scales.

edit: added socket.io part

pubnub• 10 years ago

I love NodeJS. So many NPM's to be had. I want to open source our ANSI-C Realtime Server - maybe someday. Our https://www.pubnub.com/blocks-catalog/ BLOCKS engine actually starting in Java. That was a M-I-S-T-A-K-E-E-E-E. It's better now.

firdaus• 10 years ago

Can you state your stance on AGPL[1] on the website like MongoDB and RethinkDB do to put people's minds at ease.

[1] https://github.com/deepstreamIO/deepstream.io/issues/298

Deepstream.io – Open Realtime Server

Related Stories