Show HN: Deepstream.io – A scalable server for realtime webapps
deepstream.io
deepstream.io
The front-page looks really cool.
"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 designed to abstract that all away from you to be as fast as possible?
Basically, yes. see the subscribe() function.
I am not a designer so do not know what this latest web design practice is called
- 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 client?
- Can data be larger than the cache size? How is cache eviction handled?
- 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.
If I were you, I’d start by answering everyone’s questions here. These are your potential users and leaving them hanging seems odd. The next step would be answering those questions on your site.
This is the kind of service that people are going to start using for a new project (rarely are people going to switch existing infrastructure to something brand new). But any new framework, language or platform requires investment and with developer related services and tools, people are going to research first. Help them do that research efficiently.
Good luck taking this to the next level!
Again, thanks for your advice, much appreciated.
(fyi: bad link at the bottom of this page http://deepstream.io/tutorials/simple-app-using-react.html it links to the ko demo, not the react's)
(case insensitive file system on macos may be? :))
A (rudimentary) overview of the message structure can be found here: http://deepstream.io/tutorials/message-structure.html