# US 10,482,069 B1 · Method and system for implementing a version control adaptive architecture platform > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 10,482,069 B1 - Document ID: US10482069B1 - Status: Granted - Kind: B1 - Application number: 15/668,934 - Filed: 2017-08-04 - Granted: 2019-11-19 - Earliest claimed: 2017-08-04 - Assignees: JPMorgan Chase Bank, N.A. - Applicants: JPMorgan Chase Bank, N.A. - Inventors: James Todd Barnes; Farhan Ahmed; Willie L. Brown, Jr.; Stephan W. Terry - Web page: https://patentgrep.com/patent/US10482069B1 ## CPC - G06F 11/2038: {with a single idle spare processing component} - G06F 16/1873: {Versioning file systems, temporal file systems, e.g. file system supporting different historic versions of files} - G06F 9/5083: {Techniques for rebalancing the load in a distributed system} - G06F 11/1658: {Data re-synchronization of a redundant component, or initial sync of replacement, additional or spare unit} - G06F 11/2028: {eliminating a faulty processor or activating a spare} - G06F 11/2046: {where the redundant components share persistent storage (G06F11/2043 takes precedence)} - G06F 11/2094: {Redundant storage or storage space (G06F11/2056 takes precedence)} - G06F 11/2097: {maintaining the standby controller/processing unit updated (initialisation or re-synchronisation thereof G06F11/1658 and subgroups)} - G06F 11/2033: {switching over of hardware resources} - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) ## Abstract An embodiment of the present invention is directed to a version control adaptive architecture platform. The system comprises: a global load balancer that receives a read/write request from a user, the request comprising a URL, and determines a corresponding front-end web proxy server; a Proxy server that receives the request and using the URL, accesses a lookup table to determine a specific storage component and Subversion (SVN) server to route the request; and a plurality of SVN servers, where a SVN server, identified by the Proxy server, processes the request and returns a result to the user, wherein the SVN server has a corresponding Disaster Recovery (DR) server that monitors live data processed by the SVN server for failover mode upon detection of a failover event where the SVN server automatically reroutes traffic to the corresponding DR server. ## Claims ### Claim 1 A version control adaptive system comprising: a global load balancer that receives a read/write request from a user, the request comprising a URL, determines a corresponding front-end web proxy server, and transmits the request to the corresponding front-end web proxy server; a Proxy server that receives the request from the global load balancer and using the URL, accesses a lookup table to determine a specific storage component and Subversion (SVN) server to route the request, and routes the request to the specific SVN; and a plurality of SVN servers, where the SVN server, identified by the Proxy server, processes the request and returns a result to the user, wherein the SVN server has a corresponding Disaster Recovery (DR) server that monitors live data processed by the SVN server for failover mode upon detection of a failover event where the SVN server automatically reroutes traffic to the corresponding DR server. ### Claim 2 (depends on 1) The system of claim 1, wherein the failover event comprises a scheduled maintenance event. ### Claim 3 (depends on 1) The system of claim 1, wherein the lookup table is automatically synchronized against respective Production and DR NAS filers to which it is directed. ### Claim 4 (depends on 1) The system of claim 1, wherein based on the failover event, one or more backend processes are suspended. ### Claim 5 (depends on 1) The system of claim 1, wherein the URL references source code, software build and release notes. ### Claim 6 (depends on 1) The system of claim 1, wherein the SVN server comprises a plurality of Q Trees. ### Claim 7 (depends on 1) The system of claim 1, wherein DR server comprises a plurality of Q Trees. ### Claim 8 (depends on 1) The system of claim 1, wherein one or more repositories associated with the SVN server are automatically rebalanced based on load determinations. ### Claim 9 (depends on 1) The system of claim 1, wherein one or more repositories associated with the DR server are automatically rebalanced based on load determinations. ### Claim 10 (depends on 1) The system of claim 1, wherein the lookup table is automatically updated based on updates to one or more associated repositories. ### Claim 11 A computer implemented method for implementing a version control adaptive architecture, the method comprising the steps of: receiving, at a global load balancer, a read/write request from a user, the request comprising a URL; determining a corresponding front-end web proxy server; transmitting, from the global load balancer, the request to the corresponding front-end web proxy server; receiving, at the front-end web proxy server, the request from the global load balancer; using the URL, accessing a lookup table to determine a specific storage component and Subversion (SVN) server to route the request; identifying a SVN server from a plurality of SVN servers; routing, via the proxy server, the request to the SVN server; processing, at the SVN server, the request; and returning a result to the request to the user; wherein the SVN server has a corresponding Disaster Recovery (DR) server that monitors live data processed by the SVN server for failover mode upon detection of a failover event where the SVN server automatically reroutes traffic to the corresponding DR server. ### Claim 12 (depends on 11) The method of claim 11, wherein the failover event comprises a scheduled maintenance event. ### Claim 13 (depends on 11) The method of claim 11, wherein the lookup table is automatically synchronized against respective Production and DR NAS filers to which it is directed. ### Claim 14 (depends on 11) The method of claim 11, wherein based on the failover event, one or more backend processes are suspended. ### Claim 15 (depends on 11) The method of claim 11, wherein the URL references source code, software build and release notes. ### Claim 16 (depends on 11) The method of claim 11, wherein the SVN server comprises a plurality of Q Trees. ### Claim 17 (depends on 11) The method of claim 11, wherein DR server comprises a plurality of Q Trees. ### Claim 18 (depends on 11) The method of claim 11, wherein one or more repositories associated with the SVN server are automatically rebalanced based on load determinations. ### Claim 19 (depends on 11) The method of claim 11, wherein one or more repositories associated with the DR server are automatically rebalanced based on load determinations. ### Claim 20 (depends on 11) The method of claim 11, wherein the lookup table is automatically updated based on updates to one or more associated repositories.