Enhanced service validation
First Claim
1. A method for validating a new version of a service running in parallel with a previous version of the service, the method comprising:
- duplicating traffic that is inbound to the previous version of the service, for consumption in parallel by the new version of the service;
in response to write operations that are prompted by the traffic, providing the previous version of the service with regular access to a base copy of the data and providing the new version of the service with emulated write-access to a target copy of the data, wherein the service comprises a licensing service and a portion of the traffic comprises one or more license keys to the licensing service, wherein the write operations comprise write requests and wherein providing the new version of the service with the emulated write-access comprises responding to the write requests as if having written to the target copy of the data in response to the write requests, without actually writing to the target copy of the data;
evaluating non-validated replies to the traffic generated by the new version of the service against expected replies to the traffic generated by the previous version of the service to identify flaws in the new version of the service; and
synchronizing state changes that occur with respect to the base copy of the data with the target copy of the data.
1 Assignment
0 Petitions
Accused Products
Abstract
Technology is disclosed herein for validating a new version of a service running in parallel with a previous version of the service. In a validation environment, traffic is duplicated traffic that is inbound to the previous version of the service, for consumption in parallel by the new version of the service. In response to write operations that are prompted by the traffic, the previous version of the service is provided with regular access to the data while the new version of the service is provided with emulated write-access to the data. The non-validated replies to the traffic generated by the new version of the service are then evaluated against expected replies to the traffic generated by the previous version of the service, to identify flaws in the new version of the service.
25 Citations
15 Claims
-
1. A method for validating a new version of a service running in parallel with a previous version of the service, the method comprising:
-
duplicating traffic that is inbound to the previous version of the service, for consumption in parallel by the new version of the service; in response to write operations that are prompted by the traffic, providing the previous version of the service with regular access to a base copy of the data and providing the new version of the service with emulated write-access to a target copy of the data, wherein the service comprises a licensing service and a portion of the traffic comprises one or more license keys to the licensing service, wherein the write operations comprise write requests and wherein providing the new version of the service with the emulated write-access comprises responding to the write requests as if having written to the target copy of the data in response to the write requests, without actually writing to the target copy of the data; evaluating non-validated replies to the traffic generated by the new version of the service against expected replies to the traffic generated by the previous version of the service to identify flaws in the new version of the service; and synchronizing state changes that occur with respect to the base copy of the data with the target copy of the data. - View Dependent Claims (2, 3, 4, 5, 6)
-
-
7. An apparatus for validating a new version of a service running in parallel with a previous version of the service, the apparatus comprising:
-
one or more hardware computer readable storage media; a processing system coupled with the one or more hardware computer readable storage media; and program instructions stored on the one or more hardware computer readable storage media that, when executed by the processing system, direct the processing system to at least; duplicate traffic that is inbound to the previous version of the service, for consumption in parallel by the new version of the service; generate a base copy of data used to support the service via the previous version of the service; generate a target copy of the data used to support the service via the new version of the service; in response to write operations that are prompted by the traffic, provide the previous version of the service with regular access to the base copy of the data and provide the new version of the service with emulated write-access to the target copy of the data, wherein the service comprises a licensing service and a portion of the traffic comprises one or more license keys to the licensing service, and wherein the write operations comprise write requests and wherein providing the new version of the service with the emulated write-access comprises responding to the write requests as if having written to the target copy of the data in response to the write requests, without actually writing to the target copy of the data; evaluate non-validated replies to the traffic generated by the new version of the service against expected replies to the traffic generated by the previous version of the service to identify flaws in the new version of the service; and synchronize state changes that occur with respect to the base copy of the data with the target copy of the data. - View Dependent Claims (8, 9, 10, 11, 12)
-
-
13. One or more non-transitory computer readable storage media having program instructions stored thereon for validating a new version of a service running in parallel with a previous version of the service, wherein the program instructions, when executed by a processing system, direct the processing system to at least:
-
duplicate traffic that is inbound to the previous version of the service, for consumption in parallel by the new version of the service; in response to write operations that are prompted by the traffic, provide the previous version of the service with regular access to a base copy of the data and provide the new version of the service with emulated write-access to a target copy of the data, wherein the service comprises a licensing service and a portion of the traffic comprises one or more license keys to the licensing service, wherein the write operations comprise write requests and wherein the providing the new version of the service with the emulated write-access comprises responding to the write requests as if having written to the target copy of the data in response to the write requests, without actually writing to the target copy of the data; evaluate non-validated replies to the traffic generated by the new version of the service against expected replies to the traffic generated by the previous version of the service to identify flaws in the new version of the service; and synchronize state changes that occur with respect to the base copy of the data with the target copy of the data. - View Dependent Claims (14, 15)
-
Specification