Tradeoff of `Effect.Service`: Implicitly Coupling Interface with Definition

is the main "tradeoff" of Effect.Service's convenience largely that it more implicitly couples your interface with the implementation?
i.e. from the effect monorepo template: the service is AIO interface + repo (implementation)
Was this page helpful?