Virtual runtimes

Virtual runtimes is an abstraction that can be mapped to one or more runtimes.

Virtual runtimes (VRT) is a placeholder or abstraction that can be mapped to one or more runtimes. In development environments, users often lack visibility into which runtime configurations are used in higher environments, leading to the unnecessary creation of multiple runtime configurations in lower environments. Virtual runtimes map existing runtime configurations with specific logical names. These logical mappings can then be associated with runtime configurations when deployed to other environments.

You can map virtual runtimes to any runtime you want and later switch it to a different runtime. All the services referencing the older runtime automatically follow the new runtime. Virtual runtimes can be defined in the project runtimes, flow services, workflows, and REST APIs. At runtime, the system resolves virtual runtimes to their mapped cloud runtime or self-managed runtime based on the current environment.

The following are the benefits of virtual runtimes:

• Simplify the transition between development, testing, and production environments.
• Associate virtual runtimes to a runtime.
• Dynamically remap or delete mappings as your landscape evolves.