This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-06-07
Channels
- # aleph (19)
- # aws (1)
- # beginners (75)
- # boot (28)
- # cider (1)
- # cljs-dev (12)
- # cljsrn (20)
- # clojure (350)
- # clojure-argentina (1)
- # clojure-chicago (2)
- # clojure-dev (2)
- # clojure-russia (5)
- # clojure-spec (2)
- # clojure-uk (14)
- # clojure-ukraine (3)
- # clojurescript (68)
- # component (87)
- # core-async (25)
- # core-logic (13)
- # cursive (4)
- # data-science (72)
- # datascript (59)
- # datomic (15)
- # defnpodcast (7)
- # emacs (33)
- # hoplon (5)
- # immutant (73)
- # jobs (21)
- # klipse (6)
- # lumo (14)
- # off-topic (26)
- # om (23)
- # onyx (6)
- # parinfer (37)
- # protorepl (4)
- # re-frame (13)
- # ring (2)
- # rum (3)
- # spacemacs (2)
- # specter (22)
- # sql (47)
- # uncomplicate (10)
- # unrepl (79)
- # untangled (66)
- # vim (47)
- # yada (17)
Hi, I haven't used Onyx, but it's come onto my radar because I'm looking for a distributed pub-sub solution which supports load-balanced collections of subscribers (to scale event processing). Latency is a significant factor for my use-cases, as is ordering, and at-least-once delivery guarantees. My question to the channel is: should I start to go deep on Onyx and spike something out or is it simply not a good fit? I've taken a look at MQTT brokers but I cannot find a robust clustering solution that can take the abuse I'm throwing at it with my resilience tests; SNS+SQS exhibits some bad worst case latencies which rule that out in my mind.
@codeasone It’s a good fit for that, yeah. Onyx supports in-order processing for certain topologies and has at-least-once/exactly-once (for aggregations) delivery guarantees. When tuned properly, it hits single digit millisecond end-to-end latency in AWS.
Thanks @michaeldrogalis I'll take a closer look then 🙂
@codeasone Sure. You can hit us up at <mailto:[email protected]|[email protected]> if you have long, detailed questions. Otherwise lots of help to be had right here. 🙂