This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-02-25
Channels
- # beginners (20)
- # boot (25)
- # cider (1)
- # cljs-dev (7)
- # cljsjs (1)
- # cljsrn (1)
- # clojure (79)
- # clojure-austin (2)
- # clojure-berlin (13)
- # clojure-dusseldorf (1)
- # clojure-germany (7)
- # clojure-russia (10)
- # clojure-serbia (1)
- # clojure-spec (18)
- # clojure-uk (4)
- # clojured (1)
- # clojurescript (90)
- # cursive (10)
- # datomic (7)
- # emacs (14)
- # hoplon (6)
- # luminus (16)
- # lumo (4)
- # numerical-computing (2)
- # om (25)
- # om-next (1)
- # onyx (11)
- # pedestal (10)
- # protorepl (1)
- # reagent (11)
- # remote-jobs (1)
- # ring (1)
- # rum (38)
- # spacemacs (5)
- # test-check (7)
- # untangled (122)
- # vim (1)
- # yada (8)
Hi there. I’m just beginning with Onyx, and I’m looking to cache materialized views in redis. Will redis pub/sub work with onyx? I want to avoid putting the views into kafka.
I really don’t know what I’m doing, so if the question doesn’t make sense, I wouldn’t be surprised. 🙂
basically for a cqrs and event store. I’m just a little confused about how tasks that are asynchronous work together. Kafka is the standard solution?
In that case I would think Kafka would be part of your event store and redis would be a sync
ok thx. I’m digging into the the plugins to see how :input tasks work
Basically it's going to grab some number of segments from your input source and push them through the workflow
@wildermuthn we don’t currently have a supported redis input plugin, because it’s been difficult to resume from redis sources in a fault tolerant way, because we need to be able to replay from offsets, or similar. There may be ways to use it with pub / sub now. I’d have to look into how pub / sub works with redis
Ok thanks!
The main problem with the standard pub/sub methods is there is no persistence, so messages will be lost if the peers need to be reallocated. I hear redis is adding a kafka-lite type commit log though.