This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-12-07
Channels
- # adventofcode (40)
- # aws (15)
- # babashka (76)
- # beginners (39)
- # calva (6)
- # cider (3)
- # clj-kondo (3)
- # clojure (89)
- # clojure-austin (1)
- # clojure-australia (4)
- # clojure-europe (42)
- # clojure-italy (9)
- # clojure-nl (27)
- # clojure-spec (8)
- # clojure-uk (17)
- # clojurescript (9)
- # conjure (1)
- # data-science (1)
- # datomic (19)
- # deps-new (4)
- # docker (9)
- # emacs (5)
- # events (1)
- # fulcro (36)
- # kaocha (31)
- # lambdaisland (5)
- # leiningen (3)
- # membrane (3)
- # nrepl (10)
- # off-topic (31)
- # pedestal (7)
- # reveal (47)
- # shadow-cljs (35)
- # sql (9)
- # test-check (1)
- # tools-deps (24)
- # uncomplicate (12)
- # xtdb (5)
Just re-watched the re:Clojure crux part, since I could not watch it in full live. Are there any plans to add subscriptions for the GraphQL api?
A low-effort subscriptions feature (i.e. not a 3df-like / incremental dataflow implementation) is definitely on the cards in the near-term (perhaps Q1 and orthogonal to GraphQL initially). Along on the lines of: https://github.com/hasura/graphql-engine/blob/master/architecture/live-queries.md What's your domain? Are you thinking for pushing updates to frontend clients?
Don't really have a domain. Things I did on GraphQL subscriptions is more like research. But they are hairy. And for event sourcing I do need something streaming. Which is currently solved by directly using Kafka.
I imagine the crux 3df stuff would be a prerequisite to that, but that would be cool.
btw, this http endpoint only talks about a "kafka consumer" but seems to work for jdbc as well. Seems like a very handy way to do a healthcheck to know when the container is ready for traffic https://opencrux.com/reference/http.html#sync