Deployment Considerations
The deployment strategy you choose depends on factors such as your organization's policy requirements, standard processes, and governance objectives. The following are points to consider when selecting a strategy for your organization:
Realize that any deployment that involves multiple stages requires additional effort to configure and administer. Also keep in mind that the promotion process for a multi-stage environment will be more complex and time-consuming, because it involves physically exporting objects from one registry and importing them into another. You should not deploy a multi-stage configuration unless your organization has a compelling reason to do so. Aim for a deployment strategy that aligns well with your organization's SDLC process, satisfies your organization's governance objectives and uses the fewest number of stages.
If you intend to use
CentraSite for both design-time governance and run-time governance, consider using the two-stage deployment. This configuration enables you to maintain one registry for managing Web services (and associated assets) while they are in the development and testing phases of their lifecycle and another registry for configuring, deploying and monitoring Web services that are in the production phase of their lifecycle.
Although it is possible to use a single-stage deployment for both design-time and run-time governance, such a configuration is suitable only for small or mid-size environments. Do not use a single-stage deployment if you intend to use CentraSite to manage both the design-time and run-time aspects of a large number of assets.
Note: | If you expect your organization's registry to begin small and grow over time, start with a two-stage deployment rather than attempting to switch when you outgrow the single-stage configuration. |
If you will use
CentraSite only for design-time governance, consider using a single-stage deployment. Deploying a multi-stage configuration for design-time governance does not offer any benefits. You should only consider a multi-stage deployment in a design-time implementation if your organization has a specific need to physically separate the registry of assets in the pre-production phases from the registry of assets in the production phase.
