Abstract: A system to perform certain acts to indicate when an order state within an order database has been modified. The acts can include determining that an order lookup comprises an intent to cancel an order line item. The acts can also include running rules to determine whether the order line item is authorized to be cancelled by synchronizing the cancellation and pushing a cancel state asynchronously to the order database cache. When the order line item is not authorized to be cancelled, the acts can detect that the order state has not been modified. The acts can call to a caching interface to asynchronously push a not cancel state to the order state in the order database cache. The acts can publish the not cancel order state from the order database to the order database cache. The acts can display a message that the order state cannot be modified.

Abstract: The present invention is generally directed to methods, systems, and computer program products for routing order lookups from retail systems. Order data can be synchronized from the order database cache to the order database. The order database can modify an order state of one or more customer orders from the order database. An order lookup can be received from an in-store retail system channel of one or more in-store retail system channels and can indicate a database command type. A database command type can impact a state of the order database when the order data is modified. A data source can service the order lookup based on at least a timestamp of the order data associated with a customer order. A data indicator of the order data in the order lookup can be modified when the database command type impacts the state of the order database.

Abstract: A system to perform certain acts to indicate when an order state within an order database has been modified. The acts can include determining that an order lookup comprises an intent to cancel an order line item. The acts can also include running rules to determine whether the order line item is authorized to be cancelled by synchronizing the cancellation and pushing a cancel state asynchronously to the order database cache. When the order line item is not authorized to be cancelled, the acts can detect that the order state has not been modified. The acts can call to a caching interface to asynchronously push a not cancel state to the order state in the order database cache. The acts can publish the not cancel order state from the order database to the order database cache. The acts can display a message that the order state cannot be modified.

Abstract: The present invention is generally directed to methods, systems, and computer program products for routing order lookups from retail systems. Order data can be synchronized from the order database cache to the order database. The order database can modify an order state of one or more customer orders from the order database. An order lookup can be received from an in-store retail system channel of one or more in-store retail system channels and can indicate a database command type. A database command type can impact a state of the order database when the order data is modified. A data source can service the order lookup based on at least a timestamp of the order data associated with a customer order. A data indicator of the order data in the order lookup can be modified when the database command type impacts the state of the order database.

Abstract: The present invention is generally directed to methods, systems, and computer program products for synchronizing database data to a database cache. Embodiments of the invention facilitate synchronizing order data from an order management system database to an order cache. When order data is synchronized, more efficient order lookups of the order data can occur. In some embodiments, the order management system database feeds the order cache with the latest updates as relevant state for orders is modified. A trigger within the order management system database can indicate when order state is modified. The trigger is monitored. When the trigger indicates modified order state, a caching interface (e.g., a caching API) can be called to publish the modified order state to the order cache.

Abstract: The present invention is generally directed to methods, systems, and computer program products for routing order lookups from retail systems. Order data from order management system database is synchronized to an order cache. When an order lookup is received (e.g., from a retail kiosk or POS terminal), a business layer determines if the cache can appropriately service the order lookup. If so (e.g., if the order lookup does not change order state), the business layer routes the order lookup to the cache. Otherwise (e.g., if the order lookup does change order state), the business layer routes the order lookup to the order management system database. In-store retail systems can be used to lookup orders previously submitted through other channels, such as, a website or mobile application. Knowing order details for other orders can assist the customer with in-store purchasing decisions.

Abstract: The present disclosure extends to maintaining an item inventory status at an inventory cache management system. The inventory cache may be refreshed regularly by a threshold-based triggering mechanism. In embodiments, as item inventory breaches certain thresholds, the inventory cache may be refreshed with increased frequency to mitigate overselling or underselling scenarios and reduce overall network traffic for items having relatively high inventory levels.

Abstract: The present invention is generally directed to methods, systems, and computer program products for routing order lookups. Order data from order management system database is synchronized to an order cache. When an order lookup is received, a business layer determines if the cache can appropriately service the order lookup. If so, the business layer routes the order lookup to the cache. Otherwise, the business layer routes the order lookup to the order management system database. In some embodiments, order lookups configured to impact state of the order management system database (e.g., that write or change order data) are routed to the order management system database. In these same embodiments, order lookups configured to not impact state of the order management system database (e.g., that read order data) are routed to the cache.

Abstract: The present disclosure extends to maintaining an item inventory status at an inventory cache management system. The inventory cache may be refreshed regularly by a threshold-based triggering mechanism. In embodiments, as item inventory breaches certain thresholds, the inventory cache may be refreshed with increased frequency to mitigate overselling or underselling scenarios and reduce overall network traffic for items having relatively high inventory levels.

Abstract: The present invention is generally directed to methods, systems, and computer program products for synchronizing database data to a database cache. Embodiments of the invention facilitate synchronizing order data from an order management system database to an order cache. When order data is synchronized, more efficient order lookups of the order data can occur. In some embodiments, the order management system database feeds the order cache with the latest updates as relevant state for orders is modified. A trigger within the order management system database can indicate when order state is modified. The trigger is monitored. When the trigger indicates modified order state, a caching interface (e.g., a caching API) can be called to publish the modified order state to the order cache.

Abstract: The present invention is generally directed to methods, systems, and computer program products for routing order lookups. Order data from order management system database is synchronized to an order cache. When an order lookup is received, a business layer determines if the cache can appropriately service the order lookup. If so, the business layer routes the order lookup to the cache. Otherwise, the business layer routes the order lookup to the order management system database. In some embodiments, order lookups configured to impact state of the order management system database (e.g., that write or change order data) are routed to the order management system database. In these same embodiments, order lookups configured to not impact state of the order management system database (e.g., that read order data) are routed to the cache.

Abstract: The present invention is generally directed to methods, systems, and computer program products for routing order lookups from retail systems. Order data from order management system database is synchronized to an order cache. When an order lookup is received (e.g., from a retail kiosk or POS terminal), a business layer determines if the cache can appropriately service the order lookup. If so (e.g., if the order lookup does not change order state), the business layer routes the order lookup to the cache. Otherwise (e.g., if the order lookup does change order state), the business layer routes the order lookup to the order management system database. In-store retail systems can be used to lookup orders previously submitted through other channels, such as, a website or mobile application. Knowing order details for other orders can assist the customer with in-store purchasing decisions.

Abstract: In accordance with embodiments of the invention, a method is provided for performing a storage operation in a pipeline storage system in which one or more data streams containing data to be stored are written into data chunks. The method includes generating an encryption key associated with a first archive file to be stored when encryption is requested for the storage operation, encrypting the archive data from the data stream using the encryption key to create an encrypted data chunk when a data stream containing the archive file is processed in the pipeline storage system, storing the encrypted data chunk on a storage medium, and storing the encryption key in a manner accessible during a restore operation of the encrypted data chunk.

Abstract: The present disclosure extends to maintaining an item inventory status at an inventory cache management system. The inventory cache may be refreshed regularly by a threshold-based triggering mechanism. In embodiments, as item inventory breaches certain thresholds, the inventory cache may be refreshed with increased frequency to mitigate overselling or underselling scenarios and reduce overall network traffic for items having relatively high inventory levels.

Abstract: The present disclosure extends to maintaining an item inventory status at an inventory cache management system. The inventory cache may be refreshed regularly by a threshold-based triggering mechanism. In embodiments, as item inventory breaches certain thresholds, the inventory cache may be refreshed with increased frequency to mitigate overselling or underselling scenarios and reduce overall network traffic for items having relatively high inventory levels.

Abstract: In accordance with embodiments of the invention, a method is provided for performing a storage operation in a pipeline storage system in which one or more data streams containing data to be stored are written into data chunks. The method includes generating an encryption key associated with a first archive file to be stored when encryption is requested for the storage operation, encrypting the archive data from the data stream using the encryption key to create an encrypted data chunk when a data stream containing the archive file is processed in the pipeline storage system, storing the encrypted data chunk on a storage medium, and storing the encryption key in a manner accessible during a restore operation of the encrypted data chunk.

Abstract: In accordance with embodiments of the invention, a method is provided for performing a storage operation in a pipeline storage system in which one or more data streams containing data to be stored are written into data chunks. The method includes generating an encryption key associated with a first archive file to be stored when encryption is requested for the storage operation, encrypting the archive data from the data stream using the encryption key to create an encrypted data chunk when a data stream containing the archive file is processed in the pipeline storage system, storing the encrypted data chunk on a storage medium, and storing the encryption key in a manner accessible during a restore operation of the encrypted data chunk.

Abstract: A communications system having a data transfer pipeline apparatus for transferring data in a sequence of N stages from an origination device to a destination device. The apparatus comprises dedicated memory having buffers dedicated for carrying data and a master control for registering and controlling processes associated with the apparatus for participation in the N stage data transfer sequence. The processes include a first stage process for initiating the data transfer and a last Nth stage process for completing data transfer. The first stage process allocates a buffer from a predetermined number of buffers available within the memory for collection, processing, and sending of the data from the origination device to a next stage process. The Nth stage process receives a buffer allocated to the first stage process from the (N?1)th stage and to free the buffer upon processing completion to permit reallocation of the buffer.

Abstract: The invention provides a system and method for storing a copy of data stored in an information store. In one embodiment, a data agent reads one or more blocks containing the data from the information store. The data agent maps the one or more blocks to provide a mapping of the blocks, and transmits the one or more blocks and mapping to a media agent for a storage device. The media agent stores the one or more blocks in the storage device according to the mapping.

Abstract: The invention provides a system and method for storing a copy of data stored in an information store. In one embodiment, a data agent reads one or more blocks containing the data from the information store. The data agent maps the one or more blocks to provide a mapping of the blocks, and transmits the one or more blocks and mapping to a media agent for a storage device. The media agent stores the one or more blocks in the storage device according to the mapping.