Live data from Hacker News

Telepat: Real-Time, Open Source Data Sync

telepat.io

11–20 of 37 posts

Re: Telepat: Real-Time, Open Source Data Sync

#14

Like your usecase for implementing 1 to 1 chat, is there any chance you are adding examples to the repo. Would love to see how it can be implemented.

We're actually working on a full example with code and a short video, we'll add this to our website and github repos as soon as it's done

Re: Telepat: Real-Time, Open Source Data Sync

#16

Hey everyone, one of the founders here! We've written a blog post that pretty much sums up our vision on real time infrastructures and our drive for this product. Have a look: http://blog.telepat.io

Cool! Permalink for future readers: http://blog.telepat.io/2015/08/17/hello-world/

:)

Re: Telepat: Real-Time, Open Source Data Sync

#17
post #8

Just curious: How is this different from the MQTT ecosystem?

Good question, we get this asked a lot (usually in relation with companies such as PubNub or Pusher.io). It's different in a number of ways: - it's compatible with any number of protocols (we call them transports). Currently, we support websockets, APNS and GCM. MQTT could easily be added as a transport protocol for subscribing to channels - it also handles data aggregation (for example if you have a large number of updates on an object in a short amount of time, the system will aggregate them and send only the relevant updates to the subscriber) - it's more open (in my opinion) as it's designed to enable developers to swap out one component for another (and writing a thin adapter for it if it's not already available). This should also mean that the whole system can be better optimized depending on the workload type and use-case.

Re: Telepat: Real-Time, Open Source Data Sync

#19

looks great - will you been adding offline support? mainly ability to sync changes made offline on clients back to server and handle conflicts?

Thanks! Offline support is on the roadmap - the iOS and Android clients actually already use a local database, so we're nearly there.

Re: Telepat: Real-Time, Open Source Data Sync

#20
post #8

Just curious: How is this different from the MQTT ecosystem?

Good question, we get this asked a lot (usually in relation with companies such as PubNub or Pusher.io). It's different in a number of ways: - it's compatible with any number of protocols (we call them transports). Currently, we support websockets, APNS and GCM. MQTT could easily be added as a transport protocol for subscribing to channels - it also handles data aggregation (for example if you have a large number of…

Thank you for the clarification!
Post reply on HN