This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-07-23
Channels
- # beginners (169)
- # boot (8)
- # cider (20)
- # cljdoc (66)
- # cljs-dev (1)
- # cljsrn (1)
- # clojure (185)
- # clojure-greece (11)
- # clojure-italy (16)
- # clojure-nl (5)
- # clojure-spec (16)
- # clojure-uk (39)
- # clojurescript (11)
- # cursive (26)
- # data-science (2)
- # datavis (1)
- # datomic (40)
- # emacs (10)
- # figwheel-main (64)
- # graphql (10)
- # hyperfiddle (1)
- # jobs (2)
- # leiningen (9)
- # luminus (3)
- # nyc (1)
- # off-topic (19)
- # om (1)
- # onyx (6)
- # pedestal (2)
- # re-frame (35)
- # reagent (17)
- # ring-swagger (9)
- # rum (1)
- # shadow-cljs (42)
- # spacemacs (8)
- # specter (7)
- # tools-deps (4)
- # yada (6)
I seem to remember talks about a standalone/embedded onyx for smaller deployments a while back. Is there something available or was it just an idea?
@nha Just an idea - we didn't end up pursuing it. I still think it's worthwhile, though.
I see. I was thinking it would be nice to build a work queue (not sure how this is called usually) on top of Onyx. In a one-node setup where work is not really distributed (yet) but the app could benefit from retries, maybe monitoring, persistence of jobs across restarts etc. So something like a stuartsierra/component encapsulating an Onyx instance would be great for me. Does that make sense?
It might be a bit cumbersome depending on your job execution time. Onyx defaults are setup for low latency message processing so if you’re doing something that takes a while in each of your tasks you may have to fiddle with the default timeouts a bit.
Ah that sounds like a good fit then