I think I might understand this correctly, that Effect.Service is designed to simplify service creation for a single service implementation.
What if I want to create a service with different implementations, where the differences can't be abstracted away into dependencies?
For example, if I wanted a service tagged as 'FooService', with implementations 'FooBar' and 'FooBaz', can i use Effect.Service to do this e.g. to use the same Tag for two different implementations? I see Effect.updateService but not sure if this is intended to replace the default implementation with another.
Do I just revert to the Context.Tag and creating my own layers?