Started wondering why the duct.database.sql.Boundary record is in that namespace? Couldn't a boundary be something other than a database, too, like a REST API? Just wondering whether something like duct.service.Boundary or something might be more appropriate. Or maybe I'm misunderstanding something.

I’ve been using a boundary per service - so its nice to have a database boundary, a different boundary for a REST API, etc…

Each boundary with a separate entry in config.edn

Like I have a boundary for the slack api that is just (defrecord Boundary [token])

One advantage of having separate boundaries for different services is that you get type errors if you try to use one boundary function with the wrong service type. It also keeps the services distinct.

and then protocols for different aspects of the slack api - i.e DiaglogBoundary