Deployment Strategies for Production Environments

When deploying multiple packages that are used by one or more applications, consider whether to use a shared, dependent, or independent deployment strategy.

A deployment strategy is typically determined by the availability, capacity, and versioning requirements of the applications that access the package logic in order to consume enterprise data.

• Shared Deployment Strategy
  In a shared deployment approach for packages belonging to a native development model, consider an application for mobile banking that relies on different packages to manage data relating to investment management, account management, and that offers a combined view for credit management. One deployment strategy is to deploy all packages as one mobile banking unit.
• Dependent Deployment Strategy
  With a dependent deployment strategy, some packages are published individually, as standalone units, while others are combined and published as multipackage units. In addition, rather than have a single M-Banking application, each feature is provisioned and installed separately.
• Independent Deployment Strategy
  In independent deployment, the applications are still provisioned and installed on the device separately, and the packages they are assigned to are deployed separately by including all MBOs used by the application in a single package. There are no external dependencies in this strategy.