Abstract: Multi-node resiliency may provide two or more points in a blockchain architecture from which a restarted peer can synchronize its local ledger with local ledgers of other peers that collectively form a distributed ledger. Storage-based resiliency may include providing storage that is separate from the nodes on which peers execute, and configuring a peer to store a copy of a synchronized local ledger to storage prior to restart, and synchronizing a new instance of a local ledger with the synchronized copy from storage upon restarting the peer. Peer-based resiliency may include obtaining a synchronized local ledger or genesis block from a first peer after restarting a second peer. Another point of resiliency may be provided by an orderer cluster that distributes blocks to the peers for committing to their local ledger. A peer may access obtain a synchronized ledger or genesis block from the orderer cluster upon restart.

Abstract: Multi-node resiliency may provide two or more points in a blockchain architecture from which a restarted peer can synchronize its local ledger with local ledgers of other peers that collectively form a distributed ledger. Storage-based resiliency may include providing storage that is separate from the nodes on which peers execute, and configuring a peer to store a copy of a synchronized local ledger to storage prior to restart, and synchronizing a new instance of a local ledger with the synchronized copy from storage upon restarting the peer. Peer-based resiliency may include obtaining a synchronized local ledger or genesis block from a first peer after restarting a second peer. Another point of resiliency may be provided by an orderer cluster that distributes blocks to the peers for committing to their local ledger. A peer may access obtain a synchronized ledger or genesis block from the orderer cluster upon restart.

Abstract: Multi-node resiliency may provide two or more points in a blockchain architecture from which a restarted peer can synchronize its local ledger with local ledgers of other peers that collectively form a distributed ledger. Storage-based resiliency may include providing storage that is separate from the nodes on which peers execute, and configuring a peer to store a copy of a synchronized local ledger to storage prior to restart, and synchronizing a new instance of a local ledger with the synchronized copy from storage upon restarting the peer. Peer-based resiliency may include obtaining a synchronized local ledger or genesis block from a first peer after restarting a second peer. Another point of resiliency may be provided by an orderer cluster that distributes blocks to the peers for committing to their local ledger. A peer may access obtain a synchronized ledger or genesis block from the orderer cluster upon restart.

Abstract: A system may include a first device to provide a uniform resource identifier (URI) resolution or routing service among a first data center and a second data center. The first device may provide a first failover service among devices associated with the first data center for a set of interfaces. The system may include a first set of devices and a second set of devices associated with a first application and a second application. The first device may provide a second failover service for the first and second sets of devices. The system may include a first database cluster to provide software or a service related to clustering another set of devices or providing a threshold level of availability for the other set of devices. The first database cluster may provide a failover service for the other set of devices.

Abstract: Multi-node resiliency may provide two or more points in a blockchain architecture from which a restarted peer can synchronize its local ledger with local ledgers of other peers that collectively form a distributed ledger. Storage-based resiliency may include providing storage that is separate from the nodes on which peers execute, and configuring a peer to store a copy of a synchronized local ledger to storage prior to restart, and synchronizing a new instance of a local ledger with the synchronized copy from storage upon restarting the peer. Peer-based resiliency may include obtaining a synchronized local ledger or genesis block from a first peer after restarting a second peer. Another point of resiliency may be provided by an orderer cluster that distributes blocks to the peers for committing to their local ledger. A peer may access obtain a synchronized ledger or genesis block from the orderer cluster upon restart.

Abstract: A system may include a first device to provide a uniform resource identifier (URI) resolution or routing service among a first data center and a second data center. The first device may provide a first failover service among devices associated with the first data center for a set of interfaces. The system may include a first set of devices and a second set of devices associated with a first application and a second application. The first device may provide a second failover service for the first and second sets of devices. The system may include a first database cluster to provide software or a service related to clustering another set of devices or providing a threshold level of availability for the other set of devices. The first database cluster may provide a failover service for the other set of devices.

Abstract: A system may include a first device to provide a uniform resource identifier (URI) resolution or routing service among a first data center and a second data center. The first device may provide a first failover service among devices associated with the first data center for a set of interfaces. The system may include a first set of devices and a second set of devices associated with a first application and a second application. The first device may provide a second failover service for the first and second sets of devices. The system may include a first database cluster to provide software or a service related to clustering another set of devices or providing a threshold level of availability for the other set of devices. The first database cluster may provide a failover service for the other set of devices.

Abstract: A system may include a first device to provide a uniform resource identifier (URI) resolution or routing service among a first data center and a second data center. The first device may provide a first failover service among devices associated with the first data center for a set of interfaces. The system may include a first set of devices and a second set of devices associated with a first application and a second application. The first device may provide a second failover service for the first and second sets of devices. The system may include a first database cluster to provide software or a service related to clustering another set of devices or providing a threshold level of availability for the other set of devices. The first database cluster may provide a failover service for the other set of devices.

Abstract: A computer extracts traffic data from one or more traffic servers and stores the traffic data in a database. The computer also extracts and stores customer wait time, resource management, and point of sale (POS) data from one or more retail store servers in the database, and each of the retail store servers can correspond to a retail store. Extract and store subroutines may be executed in parallel using multithreading. Upon achieving synchronization of the parallel subroutines, the computer transforms the traffic, customer wait time, resource management, and POS data from the database by determining one or more metrics for each of the retail stores. Next, the computer loads the one or more determined metrics into the database. Finally, the computer aggregates the one or more determined metrics on at least one of a district level, region level, area level, and nation level to determine one or more aggregated metrics.

Abstract: A system and method are provided for failure management for electronic transactions. An access request is received at a first server and from a client device, for a second server. The first server determines whether the second server is functional. If the second server is non-functional, the access request is stored in a storage associated with the first server. The second server is monitored until becoming functional. During the monitoring, a status request from the client device may be received and responsive to the status request, a status update is sent to the client device. Upon determining the second server is functional, the access request is sent to the second server, a response to the access request is received from the second server, and the response is sent to the client device.

Abstract: A computing device uses an integration module to manage bulk activation orders placed for machine-to-machine (M2M) devices. The integration module is configured to receive an M2M bulk activation order from a first user, where the M2M bulk activation order has information associated with a plurality of electronic devices. The integration module provides a single extensible markup language (XML) device identification request to a first database to identify a plurality of M2M devices from the plurality of electronic devices. The integration module also requests, via an XML number reservation request, a unique number for each respective M2M device of the first plurality of M2M devices. The integration module then employs the unique numbers to activate the plurality of M2M devices. After activation, the integration module may notify the user via a notification that the plurality of M2M devices have been activated.

Abstract: A system and method are provided for failure management for electronic transactions. An access request is received at a first server and from a client device, for a second server. The first server determines whether the second server is functional. If the second server is non-functional, the access request is stored in a storage associated with the first server. The second server is monitored until becoming functional. During the monitoring, a status request from the client device may be received and responsive to the status request, a status update is sent to the client device. Upon determining the second server is functional, the access request is sent to the second server, a response to the access request is received from the second server, and the response is sent to the client device.

Abstract: A computer extracts traffic data from one or more traffic servers and stores the traffic data in a database. The computer also extracts and stores customer wait time, resource management, and point of sale (POS) data from one or more retail store servers in the database, and each of the retail store servers can correspond to a retail store. Extract and store subroutines may be executed in parallel using multithreading. Upon achieving synchronization of the parallel subroutines, the computer transforms the traffic, customer wait time, resource management, and POS data from the database by determining one or more metrics for each of the retail stores. Next, the computer loads the one or more determined metrics into the database. Finally, the computer aggregates the one or more determined metrics on at least one of a district level, region level, area level, and nation level to determine one or more aggregated metrics.

Abstract: A computing device uses an integration module to manage bulk activation orders placed for machine-to-machine (M2M) devices. The integration module is configured to receive an M2M bulk activation order from a first user, where the M2M bulk activation order has information associated with a plurality of electronic devices. The integration module provides a single extensible markup language (XML) device identification request to a first database to identify a plurality of M2M devices from the plurality of electronic devices. The integration module also requests, via an XML number reservation request, a unique number for each respective M2M device of the first plurality of M2M devices. The integration module then employs the unique numbers to activate the plurality of M2M devices. After activation, the integration module may notify the user via a notification that the plurality of M2M devices have been activated.