Determining a distributed system topology from a single application deployment
Systems and methods for determining a topology of an application deployment on a distributed system can include receiving multiple traces of requests within an application, where the application includes multiple components. They can also include determining a number of times that each span between the components is traversed by a trace and associating each span with a corresponding weight reflecting the number of times that the span is traversed. Such systems and methods can further include selecting a deployment scenario based on the respective weights of each of the spans.
1. A method comprising:
receiving, by a processing device, a plurality of traces of requests within an application, wherein the application comprises a plurality of components;
determining a number of times that each span between the components is traversed by a trace of the plurality of traces;
associating each span with a corresponding weight reflecting the number of times that the span is traversed; and
selecting a deployment scenario based on the respective weights of each of the spans.
2. The method of claim 1 , further comprising deploying the components of the application according to the deployment scenario.
3. The method of claim 2 , wherein deploying the components comprises: responsive to determining that the span between a pair of components satisfies a threshold criterion, merging the pair of components.
4. The method of claim 2 , wherein deploying the components comprises: responsive to determining that the span between a pair of merged components does not satisfy a threshold criterion, splitting the merged components.
5. The method of claim 2 , wherein each component of the plurality of components is a microservice of the application.
6. The method of claim 2 , wherein deploying the components comprises grouping a set of components such that each component of the set has a span with a corresponding weight exceeding a threshold and deploying the components of the set at a same location.
7. The method of claim 2 , wherein deploying the components comprises determining components having spans below a threshold value and deploying a first component of the determined components at a different location than a second component of the determined components.
8. A system comprising:
a memory; and
a processing device coupled to the memory, the processing device configured to:
receive a plurality of traces of requests within an application, wherein the application comprises a plurality of components;
determine a number of times that each span between the components is traversed by a trace of the plurality of traces;
associate each span with a corresponding weight reflecting the number of times that the span is traversed; and
select a deployment scenario based on the respective weights of each of the spans.
9. The system of claim 8 , wherein the processing device is further configured to deploy the components of the application according to the deployment scenario.
10. The system of claim 9 , wherein deploying the components comprises, responsive to determining that the span between a pair of components satisfies a threshold criterion, merging the pair of components.
11. The system of claim 9 , wherein deploying the components comprises, responsive to determining that the span between a pair of merged components does not satisfy a threshold criterion, splitting the merged components.
12. The system of claim 9 , wherein each component of the plurality of components is a microservice of the application.
13. The system of claim 9 , wherein deploying the components comprises grouping a set of components such that each component of the set has a span with a corresponding weight exceeding a threshold and deploying the components of the set at a same location.
14. The system of claim 9 , wherein deploying the components comprises determining components having spans below a threshold value and deploying a first component of the determined components at a different location than a second component of the determined components.
15. A non-transitory machine-readable storage medium including instructions that, when accessed by a processing device, cause the processing device to:
receive a plurality of traces of requests within an application, wherein the application comprises a plurality of components;
determine a number of times that each span between the components is traversed by a trace of the plurality of traces;
associate each span with a corresponding weight reflecting the number of times that the span is traversed; and
select a deployment scenario based on the respective weights of each of the spans.
16. The non-transitory machine-readable storage medium of claim 15 , wherein the instructions further cause the processing device to deploy the components of the application according to the deployment scenario.
17. The non-transitory machine-readable storage medium of claim 16 , wherein deploying the components comprises, responsive to determining that the span between a pair of components satisfies a threshold criterion, merging the pair of components.
18. The non-transitory machine-readable storage medium of claim 16 , wherein deploying the components comprises responsive to determining that the span between a pair of merged components does not satisfy a threshold criterion, splitting the merged components.
19. The non-transitory machine-readable storage medium of claim 16 , wherein deploying the components comprises grouping a set of components such that each component of the set has a span with a corresponding weight exceeding a threshold and deploying the components of the set at a same location.
20. The non-transitory machine-readable storage medium of claim 16 , wherein deploying the components comprises identifying components having spans below a threshold value and deploying a first component of the identified components at a different location than a second component of the identified components.