This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-10-30
Channels
- # aleph (4)
- # announcements (5)
- # architecture (1)
- # aws (5)
- # babashka (12)
- # beginners (143)
- # chlorine-clover (4)
- # cider (16)
- # clj-kondo (44)
- # cljfx (26)
- # cljsrn (2)
- # clojure (34)
- # clojure-europe (28)
- # clojure-gamedev (1)
- # clojure-nl (3)
- # clojure-provo (2)
- # clojure-spec (6)
- # clojure-uk (17)
- # clojurescript (99)
- # code-reviews (6)
- # core-async (15)
- # cryogen (9)
- # cursive (14)
- # data-science (1)
- # datomic (16)
- # duct (1)
- # events (4)
- # exercism (1)
- # figwheel-main (3)
- # fulcro (3)
- # hugsql (7)
- # leiningen (4)
- # malli (15)
- # off-topic (13)
- # pathom (8)
- # re-frame (7)
- # reitit (35)
- # remote-jobs (1)
- # sci (10)
- # shadow-cljs (32)
- # sql (5)
- # tools-deps (102)
- # tree-sitter (3)
- # uncomplicate (7)
- # vim (40)
- # xtdb (8)
FYI, https://ask.clojure.org is in maintenance mode right now as I sort through some updates, should be back on tomorrow. sorry for the inconvenience
Hi all, Piped is a new library for processing messages from Amazon's Simple Queue Service (SQS). It makes use of aws-api and core.async to implement a message processing machine with easy-to-implement hooks for user space code. Feedback and issue reports are certainly welcome as it's quite young. Find it at https://github.com/RutledgePaulV/piped. Main Features: - lightweight (no amazonica!) - graceful shutdown sequence - automatic lease extensions - batches calls to aws for receiving and acking - decent performance (still need to benchmark others though) - supports blocking and non-blocking consumers
yep, no need to use core.async as a user! but optionally you can return a channel from a handler with a result of :ack or :nack.. I should document that part 🙂