Reimagining Service Definitions with Single Operations and Layered Data Requirements
I was wondering if this mental model shift would work well in all cases, or if it could cohexist with the actual way, and if it's easily and comfortably doable with existing effect combinators (and of course if it's advised not to proceed further with it 
).
Right now services have a bunch of impls, like n methods or functions, and potentially some data that they store inside.
What if you define services as the single operations and define the (eventual) data they need to have access to as an additional requirement, and then a "service" becomes a collection of layers provided all together / the necessary ones?
Example right now:
).Right now services have a bunch of impls, like n methods or functions, and potentially some data that they store inside.
What if you define services as the single operations and define the (eventual) data they need to have access to as an additional requirement, and then a "service" becomes a collection of layers provided all together / the necessary ones?
Example right now:
Similar Threads
Was this page helpful?
