Ask HN: WebSocket data architecture strategies: idempodent vs. incremental data?
How have you guys architected your data over websockets? Do you use certain strategies to reduce latency with less data over the wire and/or strategies to ensure local memory doesn't exceed a certain amount?
(
8 comments
| 3 points
| on HN
)
For example, check out the docs for the Binance websockets (they use both snapshot and delta messages): https://github.com/binance/binance-spot-api-docs/blob/master...
If you could tell me a little more about the data format, data volumes, number of subscribers, and how you get the data on the backend, I can try to give you some more concrete advice.
There are fancier versions of this scheme that can be devised based on the business rules for your application.
I’ve learned a lot from reading about the architecture of existing distributed systems e.g CouchDb, Git, and Bitcoin.
did you try going for a 3rd party provider like Firebase, Ably or Pubnub?