The cloud-native orchestrator for the whole development lifecycle, with integrated lineage and observability.

dagster

Is a resource only persistent within a solid, or can it persist from solid to solid?

For example, if I write a resource that uses a singleton to produce data, and the singleton is called in SolidA, when the resource is used and the singleton is called in SolidB will it yield its cached value, or will it be a brand new instance of the resource?

all executors except for `in_process` have process level isolation for the execution of each solid, so the resources get spun up in each step execution subprocess

Ok, that does make sense and is actually very reasonable.