4 ms·

Thanks, any plan for the android client?

• wolframhempel 10y ago
  sorry, not quite following. There is an android client here: https://deepstream.io/install/android/ https://deepstream.io/install/android/
  • reactor 10y ago
    Ah sorry, didn't notice.
  • reactor 10y ago
    Looks quite interesting, I was evaluating few real-time frameworks (esp socket.io) for the past couple of days . Could you pls shed some lights on how easy to use deepstream to setup a one-to-one in-app chat/messaging setup for android? I guess its the event's are the way to go. For eg: client.event.subscribe('channel1', eventCallback) client.event.emit('channel1', 'hello how are you?') How scalable is that? can it support thousands of channels without any hiccups on a single medium digital ocean instance?
    • wolframhempel 10y ago
      It scales very far. We've conducted benchmarks lately that showed that a single deepstream on an AWS t2.medium instance can comfortably handle 160.000~200.000 messages a second and a cluster of six ~ 4 Billion an hour. Please find the detailed results here https://deepstream.io/info/performance/four-billion-messages-per-hour/ https://deepstream.io/info/performance/four-billion-messages... For your chat though you need to consider whether your messages will be persistent and mutable (changeable after they've been posted) or are just one-off messages. In the first case using a list (https://deepstream.io/tutorials/core/datasync-lists/ https://deepstream.io/tutorials/core/datasync-lists/) with references to records (https://deepstream.io/tutorials/core/datasync-records/ https://deepstream.io/tutorials/core/datasync-records/) is the way to go, in the second case pub/sub (https://deepstream.io/tutorials/core/pubsub-events/ https://deepstream.io/tutorials/core/pubsub-events/) might be better
      • stemuk 10y ago
        Do lists offer pagination for lazy-loading?