Abstract: A system may include a first point of deployment (POD) and a second POD at a data center, where each of the first POD and the second POD may be configured to support a first version of a platform template. The first POD may a first set of servers based on a first hardware platform and the second POD may include a second set of servers based on a second hardware platform. A configuration manager may be configured to determine a difference between the first hardware platform and the second hardware platform and generate a second version of the platform template based on the difference between the first hardware platform associated and the second hardware platform. In some cases, the second version of the platform template may be installed on the second POD as part of an upgrade process.

Abstract: A system may include an active first point of deployment (POD) configured to provide a specified business functionality and may include a first server and a first instance of a platform to provide the specified business function. A dark second POD may be configured to include a second server and a second instance of the platform template, where the first platform template instance comprises a different version than the second platform template instance. A POD management computing device may test an operation of the second POD in parallel with the operation of the first POD. The POD management computing device may upgrade the business functionality by deactivating the first POD and activating the second POD to provide the specified business function using the second instance of the platform template.

Abstract: A system associated with a data center may include an active first point of deployment (POD) configured to provide a business functionality to users communicating via a network based on a first version of a platform template, a dark second POD configured with a different second version of the platform template and a switching tool to manage communication to and from the first POD and the second POD. The switching tool may send a received message the message to the destination based, at least in part, on the source of the received message, where the switching tool may send messages received from user devices to the first data center and may send messages received from testing devices to the second data center. The switching tool may, in response to a switching command, switch operation of the business functionality from the first POD to the second POD.

Abstract: A system may include a first point of deployment (POD) and a second POD at a data center, where each of the first POD and the second POD may be configured to support a first version of a platform template. The first POD may a first set of servers based on a first hardware platform and the second POD may include a second set of servers based on a second hardware platform. A configuration manager may be configured to determine a difference between the first hardware platform and the second hardware platform and generate a second version of the platform template based on the difference between the first hardware platform associated and the second hardware platform.

Abstract: A system may include an active first point of deployment (POD) configured to provide a specified business functionality and may include a first server and a first instance of a platform to provide the specified business function. A dark second POD may be configured to include a second server and a second instance of the platform template, where the first platform template instance comprises a different version than the second platform template instance. A POD management computing device may test an operation of the second POD in parallel with the operation of the first POD. The POD management computing device may upgrade the business functionality by deactivating the first POD and activating the second POD to provide the specified business function using the second instance of the platform template.

Abstract: Embodiments of the prevent invention allow a primary user to create a dependent account in order to control and monitor the transactions made by a dependent user. The primary user can limit the transactions that the dependent user can make at a store or for products. The primary user can set transaction amount limits and transaction time limits on the transactions the dependent user can make. The primary user may also set allocation limits that limit the amount of an allowed transaction that can be applied to the dependent account. The difference between the allowed transaction amount and the allocation limit amount is paid for through the use of another account. The alternate account may be pre-determined, may be determined at the time of the transaction, or at a later point in time after the transaction has been completed between the dependent user and the merchant.

Abstract: Embodiments of the prevent invention allow a primary user to create a dependent account in order to control and monitor the transactions made by a dependent user that is authorized to use the dependent account. The primary user can limit the transactions that the dependent user can make at a store or for products. The primary user can set transaction amount limits and transaction time limits on the transactions the dependent user can make at the blocked/approved stores or on the blocked/approved products. The primary user can set other limits, such as transaction type limits (e.g., in store purchase vs online purchase, or the like), location limits (e.g., radius location, zip code, state, region, or the like), or variance limits (e.g., particular transactions may be a percentage or dollar amount over the limits).