Definition of "execution boundary"

[ptbrowne]

What is the problem this feature would solve?

I am following the Effect advanced workshop video on Youtube, and multiple times, the term "execution boundary" is used, and I am struggling to find a good definition for that. I get that in an Express server, somehow each request should have their own independent context, and should not be dependent on any other, such that if one request fail, it should not make other requests fail, and maybe that's the definition of execution boundary ?

What is the feature you are proposing to solve the problem?

Having a definition in the glossary would be helpful. Local and distributed workflow definitions could link to it.

What alternatives have you considered?

Maybe it's a known concept from elsewhere that I do not know 😅

[mikearnaldi]

Execution boundary means any time you need to run an effect, ergo execute it. In an express example you do want to share context between requests, for example you want to share every service to not re-construct it, as the examples in the advanced workshop show. The concept is introduced when we talk about runtimes, https://effect.website/docs/guides/runtime not sure we should re-introduce it in the glossary