This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-10-01
Channels
- # beginners (2)
- # boot (1)
- # cljs-dev (126)
- # cljsrn (4)
- # clojars (1)
- # clojure (109)
- # clojure-austin (5)
- # clojure-austria (1)
- # clojure-boston (2)
- # clojure-brasil (33)
- # clojure-canada (1)
- # clojure-russia (1)
- # clojure-spec (62)
- # clojurescript (23)
- # core-async (1)
- # cursive (33)
- # datomic (26)
- # ethereum (2)
- # hoplon (7)
- # jobs (1)
- # lein-figwheel (1)
- # luminus (12)
- # off-topic (4)
- # om (3)
- # om-next (49)
- # perun (2)
- # protorepl (2)
- # specter (6)
- # test-check (1)
- # untangled (2)
- # vim (6)
- # yada (30)
I’m trying to understand the reasoning of this SO answer. Why would it be better to offload stuff to Redis instead of keeping it in RabbitMQ and consuming it slowly (db writes)? http://stackoverflow.com/questions/26617649/rabbitmq-fast-producer-and-slow-consumer/26660425#26660425
@michaelklishin I stumbled upon this code here: https://github.com/michaelklishin/rabbitmq_java_client_issue_19/blob/master/src/rabbit_generator/consumer.clj I wonder what are the trade offs between consuming with qos = n + manual ack vs offloading to redis and then consuming from redis (stackoverflow link above)