I don't see any benchmarks showing this as "faster." Seems like a pretty serious claim.<p>From the Firebase JavaScript SDK, I can do one thousand individual gets with a 3.4k payload at 1-2ms each. <a href="http://jsfiddle.net/katowulf/8wkon62c/" rel="nofollow">http://jsfiddle.net/katowulf/8wkon62c/</a><p>Mileage varies, of course, but I'd love to see a benchmark I can run side by side that can beat those numbers. I can't even get close with a simple GET, which returns in 86ms.
Not exactly Firebase in that it doesn't provide an arbitrarily nested JSON structure as a datastore but more of a document-based approach. Overall a pretty good alternative to Firebase but there is no security rules, no default data store or auth so you need a lot more work. Lists are not very good being just a record with an array of record keys and not the actual data. I use the self-hosted version (deepstream.io) at work where we can't use Firebase because of company policy and regulations.
Very interesting, I like that it's open. PubNub was on my mind, but I would need to look into this. If anyone has any experiences with PubNub vs DeepstreamHub, I'd love to know.
So, is this equivalent of Realm Mobile Platform[1]?
I found realm to be convenient to use in mobile apps. Haven't tried the mobile platform yet. Anyone here can give a quick comparison of RMP and DeepstreamHub?<p>[1]: <a href="https://realm.io/products/realm-mobile-platform/" rel="nofollow">https://realm.io/products/realm-mobile-platform/</a>
Competitor here, please don't become an "open core" company - "Open Core" = "Crippleware".<p>Here is my thoughts/arguments around it, dealing with the RethinkDB and Parse shut down as well: <a href="https://hackernoon.com/the-implications-of-rethinkdb-and-parse-shutdowns-c076460058f7" rel="nofollow">https://hackernoon.com/the-implications-of-rethinkdb-and-par...</a><p>Plus, was invited to speak about it on the Changelog Podcast: <a href="https://changelog.com/podcast/236" rel="nofollow">https://changelog.com/podcast/236</a><p>Please stay truly open :) that way we can still compete. ;) Or else we'll be the only company that is fully Open Source (replication, auto failover, etc.)!