Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: Deepstream.io – A scalable server for realtime webapps

deepstream.io

Post reply on HN
Print view View original

11–20 of 42 posts

Re: Show HN: Deepstream.io – A scalable server for realtime webapps

#11

Post by rubiquity »

sirstompsalot wrote: post #9
nbrempel wrote: post #2

I'm very excited about this! Without reading too much into this, is it safe to say it's like a self-hosted firebase? "Due to the way deepstream structures its data (JSON blobs, identified by a primary key) it is recommendable to use an Object oriented or schema-less database (e.g. MongoDB or RethinkDB), rather than a relational database like MySQL." Is there a way to run complex queries against the data or it designe…

Similarly (without reading too much about it) can I use InfluxDb instead of RethinkDb? (Disclaimer: I'm a RethinkDB fanboy, but I'd like to know my options.)

Why would you compare InfluxDB and RethinkDB? Those are two databases for very, very different problems. CouchDB and MongoDB are more comparable to RethinkDB if that helps you get a start!

Re: Show HN: Deepstream.io – A scalable server for realtime webapps

#13

Post by wolframhempel »

tristanz wrote: post #8

Very necessary. A few questions: - How big can records be? Are they stored as a single object in the persistence layer or using something like materialized paths. The firebase data model is one huge JSON structure, so this looks different. - How are conflicts handled? Last writer on server wins or last writer anywhere? Do you ensure eventual consistency of all the clients even when you apply optimistic writes on the…

Thanks - Records have no hard size limit - but are limited to the maximum size of your cache entry or database document. The tcp connection can send a single record update over multiple packets.

- Records already have a version that's incremented with every change and also persisted as part of the record's meta-data. Currently deepstream uses a simple first-wins strategy and subsequent updates for the same version number get rejected. However configurable merge strategies are in planning as part of a "record-options" setting.

- Currently data has to be explicitly deleted from the cache.

Re: Show HN: Deepstream.io – A scalable server for realtime webapps

#14

Post by wolframhempel »

degenerate wrote: post #12

Very nice self-explaining landing page! Although the bulleted list webfont renders rather poorly in Win7 Chrome: http://i.imgur.com/j0a0rAQ.png

oh dear, we'll definitely have to have a look into that. Thanks for posting the screenshot :-)

Re: Show HN: Deepstream.io – A scalable server for realtime webapps

#17

Post by oori »

nbrempel wrote: post #2

I'm very excited about this! Without reading too much into this, is it safe to say it's like a self-hosted firebase? "Due to the way deepstream structures its data (JSON blobs, identified by a primary key) it is recommendable to use an Object oriented or schema-less database (e.g. MongoDB or RethinkDB), rather than a relational database like MySQL." Is there a way to run complex queries against the data or it designe…

"it's like a self-hosted firebase"

Basically, yes. see the subscribe() function.

Re: Show HN: Deepstream.io – A scalable server for realtime webapps

#18

Post by wolframhempel »

dvliman wrote: post #16

Is there a documentation of transport protocol? i.e http sse, websocket? ...peeking the source code a little bit - tcp-socket?

Deepstream is using a TcpPort to allow for connections from other Node-processes (and hopefully, going forward Java, C++ etc..) and engine.io for browser communication. Engine.io initially connects using long-polling http and upgrades to Websocket if available.

A (rudimentary) overview of the message structure can be found here: http://deepstream.io/tutorials/message-structure.html

Post reply on HN