Given that Doohickey Cloud expands the capabilities of an integration platform (usually Open Integration Hub), an environment is a reference to an instance of that integration platform. It's where Doohickey will deploy integration data flows to enable integration on end customers' behalves. While not likely to be made up of many entries, your list of environments is effectively a registry of integration platforms, whether homegrown or commercially available, that will move data on your end users behalf.
Use environments to do the following:
- Associate Doohickey configurations and templates to the integration engine(s) that will execute data flow according to how those configuration+template combinations define.
- More specifically, connect Doohickey to instances of Open Integration Hub, if that is your integration engine of choice.
- Store aliased references to an environment's capabilities (e.g. integration components), so developers don't have to manage different IDs across instances of an integration platform
Doohickey is intentionally decoupled from the underlying integration technology that will actually move data on an end user’s behalf. This affords your team the most flexibility to unify your integration operations on Doohickey but still use integration technology other than Open Integration Hub, which is Blended Edge’s default. Keeping distinct environment registrations also empowers your team to use a mix of integration technologies, but still maintain Doohickey as your operational layer.
Leveraging multiple environments also makes it easier to leverage development, staging, and production instances of an integration platform. This empowers engineers to use the kinds of build-test-deploy workflows they are used tor for custom software development.
Integration definitions relate to the following entities:
- Environments relate to individual deployments of a given integration technology.
- Environments relate 1:1 to deployments of Open Integration Hub, if that is your integration technology of choice.
- Tenants, Connections, and Integration Configurations all use the environment configuration to interact with the integration engine.