The following table summarizes the advantages of various types of deployment:
Feature | Single Instance Benefit | Multiple Instance Benefit | Multiple Context Root Benefit | Multi- Schema Benefit |
---|---|---|---|---|
Enterprises can share inventory/capacity/catalog. | X | |||
Ship nodes can be shared across enterprises. Organizations can participate with each other. | X | |||
In the Configuration Deployment Tool (CDT), Configuration data can be compared and migrated all at once. | ||||
Enterprises can inherit rules from another enterprise within this same Configuration schema. | X | X | ||
Each enterprise can have its own code extensions, events, templates, extensions to user interfaces, menus, and user exit implementations. If two enterprises have different inventory systems, they need to have different interfaces, too. These can all be defined by enterprise. | X | X | X | X |
Each enterprise is configured separately and can have its own sourcing rules, pipelines, tasks, and so on. This isolation of configuration means that you can deploy and move data by enterprise in the Configuration Deployment Tool (CDT). | X | X | X | X |
All enterprises are under a single point of control. For example, you can start and stop agents and monitor processes from one place. | X | X | ||
Enterprises upgrade independently by enterprise, due to isolation of Transaction data. | X | X | X | |
Enterprises can increase database size and keep adding instances. | X | |||
Application server monitoring/maintenance can be performed at an aggregate level across all deployments. | X | X | X | |
Isolation of context roots can result in better and more dynamic utilization of hardware capacity, especially if you ensure that the enterprises sharing an application server require different peak usage periods. | X | X | X | |
Gain in memory utilization. For example, because Configuration data is not shared, configuration of resource permissions would be duplicated, resulting in approximately twice the memory consumption. | X | X | ||
You do not need to synchronize Configuration data, such as hub-level pipelines, that are shared by two colonies. | X | X | ||
Compared to a single-instance deployment, enterprise growth can be handled by adding smaller-sized database nodes, rather than expanding monolithic databases. Compared to a multiple-instance deployment, the capacity of the application server is better utilized. | X | |||
Enterprises can benefit from the isolated Configuration schema when using the Configuration Deployment Tool, and at the same time, be able to deploy Configuration across multiple colonies. | X |