This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-01-22
Channels
- # announcements (28)
- # babashka (77)
- # beginners (122)
- # calva (40)
- # circleci (3)
- # clj-kondo (47)
- # cljs-dev (9)
- # clojure (119)
- # clojure-australia (1)
- # clojure-europe (88)
- # clojure-nl (3)
- # clojure-uk (33)
- # code-reviews (64)
- # core-logic (37)
- # cursive (10)
- # datomic (13)
- # emacs (1)
- # fulcro (4)
- # graalvm (1)
- # graphql (5)
- # helix (4)
- # integrant (25)
- # jobs (1)
- # jobs-rus (1)
- # off-topic (3)
- # pathom (12)
- # random (1)
- # re-frame (48)
- # reagent (1)
- # remote-jobs (1)
- # reveal (1)
- # rewrite-clj (4)
- # ring (6)
- # ring-swagger (1)
- # shadow-cljs (21)
- # sql (8)
- # tools-deps (25)
- # vim (15)
- # xtdb (12)
What’s the go-to solution for a non-cloud-hostet small scale HA crux deployment? 3-nodes running kafka? (I’d hate to have to maintain that)
IIRC this basically a failover architecture which I’m not a fan of. It’s also tricky to get STOMITH right etc.
If it helps, we've used the Confluent Kafka Docker images in the past with relatively little trouble
With a basic setup I assume, you can run zookeeper and kafka nodes side by side on 3 nodes.
This looks tempting https://github.com/spotify/docker-kafka
Hi all, we've published a new dev-journal you may be interested in: https://opencrux.com/blog/dev-diary-jan-21.html.
Yeah it's definitely possible that Ketu (or similar) would simplify a few things. We currently rely on Java interop and track our own offsets, but it isn't so bad. Maybe Ketu would be a good option if our usage of Kafka grows more advanced in future. Asides from a few Java classes for serdes classes and ID partitioning, all the Kafka-related parts of Crux are handled here in a single ns: https://github.com/juxt/crux/blob/master/crux-kafka/src/crux/kafka.clj