Developer test environment with containerization of tightly coupled systems

1. A system comprising:

a distributed network comprising a plurality of servers, wherein operations of a first server and a second server of the distributed network are tightly coupled; and

an exception resolution system comprising a processor configured to:

determine that an exception error is detected in the distributed network, wherein the exception error corresponds to a failed transmission of communication data between communicatively coupled servers of the distributed network;

determine a data transfer route associated with failed transmission of the communication data, wherein the data transfer route includes the servers of the distributed network that fail to transmit or receive the communication data as a result of the exception error;

determine that the tightly coupled first server and second server are included in the data transfer route;

determine a subset of components of the tightly coupled first server and second server that are involved in operations associated with the exception error;

generate, based on the data transfer route and the subset of components, a containerized test environment comprising replica components corresponding to (1) the servers included in the data transfer route other than the first and second servers and (2) the subset of the components of the tightly coupled first and second servers that are involved in operations associated with the exception error;

provide a change to a property of a first replica component of the containerized test environment, wherein the property of the first replica component corresponds to a data transfer configuration property of the first server;

determine, based on results provided by the containerized test environment, that the provided change resolves the exception error;

store the change in a solution registry, wherein the change is stored as an executable corrective action configured to be automatically implementable to perform the change at a future time;

after storing the executable action:

detect a subsequent exception error;

determine that the stored executable action resolves the subsequent exception error; and

automatically implement the executable action, thereby automatically resolving the subsequent exception error; and

determine that the stored executable action resolves the subsequent exception error by:

determining a root cause of the subsequent exception error;

determining properties of the distributed network at the time of the subsequent exception error; and

determining, using the solution registry, that stored executable action is for the determined root cause and is associated with the determined properties of the distributed network at the time of the subsequent exception error.

2. The system of claim 1 , wherein the processor is further configured to automatically implement the change at the first server in the distributed network, wherein automatically implementing the change allows transmission of the communication data through the plurality of servers of the distributed network.

3. The system of claim 1 , wherein the containerized test environment excludes replica components for servers not included in the determined data transfer route, such that the containerized test environment is executable without wasting computational resources to replicate operations of servers not included in the determined data transfer route.

4. The system of claim 1 , wherein the data configuration property corresponds to a connection timing parameter for communications between the first server and one or more other servers of the distributed network.

5. A method, comprising:

determining that an exception error is detected in a distributed network comprising a plurality of servers, wherein operations of a first server and a second server of the distributed network are tightly coupled, wherein the exception error corresponds to a failed transmission of communication data between communicatively coupled servers of the distributed network;

determining a data transfer route associated with failed transmission of the communication data, wherein the data transfer route includes the servers of the distributed network that fail to transmit or receive the communication data as a result of the exception error;

determining that the tightly coupled first server and second server are included in the data transfer route;

determining a subset of components of the tightly coupled first server and second server that are involved in operations associated with the exception error;

generating, based on the data transfer route and the subset of components, a containerized test environment comprising replica components corresponding to (1) the servers included in the data transfer route other than the first and second servers and (2) the subset of the components of the tightly coupled first and second servers that are involved in operations associated with the exception error;

providing a change to a property of a first replica component of the containerized test environment, wherein the property of the first replica component corresponds to a data transfer configuration property of the first server;

determining, based on results provided by the containerized test environment, that the provided change resolves the exception error;

storing the change in a solution registry, wherein the change is stored as an executable corrective action configured to be automatically implementable to perform the change at a future time;

after storing the executable action:

detecting a subsequent exception error;

determining that the stored executable action resolves the subsequent exception error; and

automatically implementing the executable action, thereby automatically resolving the subsequent exception error; and

determining that the stored executable action resolves the subsequent exception error by:

determining a root cause of the subsequent exception error;

determining properties of the distributed network at the time of the subsequent exception error; and

determining, using the solution registry, that stored executable action is for the determined root cause and is associated with the determined properties of the distributed network at the time of the subsequent exception error.

6. The method of claim 5 , further comprising automatically implementing the change at the first server in the distributed network, wherein automatically implementing the change allows transmission of the communication data through the plurality of servers of the distributed network.

7. The method of claim 5 , wherein the containerized test environment excludes replica components for servers not included in the determined data transfer route, such that the containerized test environment is executable without wasting computational resources to replicate operations of servers not included in the determined data transfer route.

8. The method of claim 5 , wherein the data configuration property corresponds to a connection timing parameter for communications between the first server and one or more other servers of the distributed network.

9. A non-transitory computer-readable medium storing instructions that when executed by a processor cause the processor to:

determine that an exception error is detected in a distributed network comprising a plurality of servers, wherein operations of a first server and a second server of the distributed network are tightly coupled, wherein the exception error corresponds to a failed transmission of communication data between communicatively coupled servers of the distributed network;

determine a data transfer route associated with failed transmission of the communication data, wherein the data transfer route includes the servers of the distributed network that fail to transmit or receive the communication data as a result of the exception error;

determine that the tightly coupled first server and second server are included in the data transfer route;

determine a subset of components of the tightly coupled first server and second server that are involved in operations associated with the exception error;

generate, based on the data transfer route and the subset of components, a containerized test environment comprising replica components corresponding to (1) the servers included in the data transfer route other than the first and second servers and (2) the subset of the components of the tightly coupled first and second servers that are involved in operations associated with the exception error;

provide a change to a property of a first replica component of the containerized test environment, wherein the property of the first replica component corresponds to a data transfer configuration property of the first server;

determine, based on results provided by the containerized test environment, that the provided change resolves the exception error;

store the change in a solution registry, wherein the change is stored as an executable corrective action configured to be automatically implementable to perform the change at a future time;

after storing the executable action:

detect a subsequent exception error;

determine that the stored executable action resolves the subsequent exception error; and

automatically implement the executable action, thereby automatically resolving the subsequent exception error; and

determine that the stored executable action resolves the subsequent exception error by:

determining a root cause of the subsequent exception error;

determining properties of the distributed network at the time of the subsequent exception error; and

determining, using the solution registry, that stored executable action is for the determined root cause and is associated with the determined properties of the distributed network at the time of the subsequent exception error.

10. The non-transitory computer-readable medium of claim 9 , wherein the instructions when executed by the processor further cause the processor to automatically implement the change at the first server in the distributed network, wherein automatically implementing the change allows transmission of the communication data through the plurality of servers of the distributed network.

11. The non-transitory computer-readable medium of claim 9 , wherein the containerized test environment excludes replica components for servers not included in the determined data transfer route, such that the containerized test environment is executable without wasting computational resources to replicate operations of servers not included in the determined data transfer route.