805 karma · joined August 21, 2012
[ my public key: https://keybase.io/jensrantil; my proof: https://keybase.io/jensrantil/sigs/lxsQ3_wfe5J1Akf75bO42UAhjVdv3TPY0WoT01wbMJA ]
...and yes, we support 2FA. ;)
Also my OCD kicks in with sometimes colons. Additionally, periods in commit messages...
Also, NATS has client libraries for many languages that adds request/response semantics on top of the pub/sub semantics.
I'm not a native English speaker and was expecting s/in/with since I read you are not allowed to use shark fins as transportation for trade.
IMHO the most reliable way to get data from point A to point B is likely by having a client actively polling for data, using a strict socket timeout. Data should be at-least once delivered. If JSONS should be called anything remotely "reliable" as periodically polling, at least it should have a strict timeout (not mentioned in the article) for receiving the next newline & it should handle replaying of non-acked messages. Otherwise I would call it far from "reliable".