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.
For example, being able to review investment data is a frequently used feature of mobile banking, the Investment packages allows the application user to check the changing status of a stock portfolio. Whereas, the Account Management packages might be used by the M-Banking application more sporadically. Both Investment and Account Management depend on Credit Management packages for data management, but because both have unique capacity and availability requirements, sharing packages is less of a concern.
However, the key limitation with shared deployment is versioning relating to changes or major enhancements to either the application or the packages it relies on. In this strategy all packages and all applications must be maintained simultaneously.
