This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-10-13
Channels
- # announcements (1)
- # babashka (30)
- # beginners (43)
- # biff (24)
- # calva (72)
- # cider (12)
- # clj-commons (24)
- # clj-on-windows (10)
- # cljsrn (23)
- # clojure (123)
- # clojure-bay-area (6)
- # clojure-europe (43)
- # clojure-losangeles (2)
- # clojure-nl (2)
- # clojure-uk (9)
- # clojurescript (125)
- # core-async (9)
- # cursive (2)
- # data-science (3)
- # datomic (30)
- # devops (1)
- # emacs (13)
- # events (5)
- # fulcro (15)
- # graalvm (3)
- # gratitude (1)
- # humbleui (11)
- # lsp (5)
- # nbb (24)
- # off-topic (11)
- # pedestal (5)
- # releases (1)
- # remote-jobs (1)
- # sci (15)
- # scittle (16)
- # shadow-cljs (15)
- # sql (11)
- # tools-deps (9)
- # xtdb (5)
Imagine you have a Clojure backend, a Python backend and a frontend team (all working independently from each other, different release cycles etc) and a pipeline that caters for a specific use case (e.g. a background job that does a specific computation and involves all of the teams). If you were to add SNS topics, where would you put them? 1. a Clojure backend topic, a Python backend topic and a frontend topic, each team would be a publisher to their own topic -> clear bounded contexts/ownership of topics but it's the responsibility of the subscribers to figure out which topic to subscribe to (a kind of complexity? ) 2. A single topic specific to the pipeline, shared by all the teams -> simpler design, publishers and subscribers don't need to know about each other but none of the teams has the ownership/control of the topic it publishes to (it has to go under the jurisdiction of the DevOps team)