This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-07-21
Channels
- # aws (14)
- # babashka (35)
- # beginners (163)
- # boot (2)
- # calva (5)
- # cider (30)
- # clojure (143)
- # clojure-colombia (1)
- # clojure-europe (5)
- # clojure-nl (11)
- # clojure-spec (1)
- # clojure-uk (16)
- # clojurescript (71)
- # community-development (2)
- # conjure (1)
- # cursive (6)
- # datomic (30)
- # duct (4)
- # figwheel-main (11)
- # fulcro (28)
- # graalvm (3)
- # graphql (23)
- # hoplon (36)
- # jackdaw (24)
- # kaocha (16)
- # lambdaisland (1)
- # leiningen (4)
- # luminus (3)
- # meander (4)
- # observability (1)
- # off-topic (10)
- # pathom (5)
- # re-frame (27)
- # reitit (7)
- # remote-jobs (1)
- # sci (17)
- # shadow-cljs (22)
- # spacemacs (14)
- # sql (61)
- # testing (3)
- # tools-deps (27)
- # vim (2)
- # xtdb (18)
- # yada (2)
hey everyone, Im having a hard time on how to wrap my head around boundaries
lets say I have a system that will make primarily http calls to other systems
id like to create a protocol + record for some sort of HTTPService
it to facilitate dependency injection, testing & etc
is this a boundary HTTPService
? Another services like the UserService
will depend on that http service .. I know UserService
should be a boundary, but it doesnt make sense for a boundary to depend on another right?
Yeah, it only really makes sense if you need the decoupling.
You’re already decoupling your app from the implementation of UserService
so the HttpService
within it is just an implementation detail and not something consumers of UserService
will need to know about.
@plins
> but it doesnt make sense for a boundary to depend on another right
I don't think there's an issue with that. The point is for the boundary interface to be implementation agnostic. So whether your UserService
uses an HTTPService
or a Shrubbery mock to do the "heavy lifting" shouldn't matter.
From a slightly different angle, UserService
could be your boundary, where HTTPService
is a dependent component (not boundary) of an implementation of UserService
.
(Disclaimer: this is my interpretation of the goals of boundaries, as described at https://github.com/duct-framework/duct/wiki/Boundaries)