Isolating pygeoapi Core Runtime from Custom Process Dependencies

[OpenGeoShift]

Dear pygeoapi community,

At the moment, both pygeoapi itself and custom processes run within the same Python runtime environment and therefore share the same versions of any common dependencies.

I am wondering whether there is a recommended approach to isolate the pygeoapi core runtime from the runtime environment of custom processes, in order to avoid potential dependency conflicts.

Is it expected that all processes align their dependencies with pygeoapi’s environment?

Or is there a supported or recommended pattern (e.g., subprocess execution, external services, custom process managers) to achieve runtime isolation?

Thank you in advance for your guidance.