Estimating latency of an application

A method comprising:

• identifying a set of server-side services that a server-side application relies on during execution of the server-side application;
• based on history data that indicates a latency that is associated with each service in the set of server-side services and that is determined based on requests from client devices that are remote relative to the set of server-side services, estimating a latency of the server-side application;
• wherein estimating the latency of the server-side application comprises:
• for each service in the set of server-side services, identifying one or more application programming interfaces (APIs), of said each service, that the server-side application is configured to call;
• identifying a first API, of a first service, that the server-side application is configured to call;
• determining a first latency associated with the first API;
• identifying a second API, of a second service, that the server-side application is configured to call, wherein the second API is different than the first API;
• determining a second latency associated with the second API;
• applying a weight to the first latency based on a number of times the first API was previously called.

A system comprising:

• one or more processors;
• one or more non-transitory storage media storing instructions which, when executed by the one or more processors, cause:
• identifying a set of server-side services that a server-side application relies on during execution of the server-side application;
• based on history data that indicates a latency that is associated with each service in the set of server-side services and that is determined based on requests from client devices that are remote relative to the set of server-side services, estimating a latency of the server-side application;
• wherein estimating the latency of the server-side application comprises, for a particular service in the set of server-side services:
• identifying one or more application programming interfaces (APIs), of the particular service, that the server-side application is configured to call;
• for each API in the one or more APIs of the particular service:
• determining a latency of said each API;
• determining a number of times the server-side application is configured to call said each API;
• based on the number of times for each API of the one or more APIs and the latency of each API of the one or more APIs, calculate a total latency of the particular service.

A system comprising:

• one or more processors;
• one or more storage media storing instructions which, when executed by the one or more processors, cause:
• identifying a set of server-side services that a server-side application relies on during execution of the server-side application;
• based on history data that indicates a latency that is associated with each service in the set of server-side services and that is determined based on requests from client devices that are remote relative to the set of server-side services, estimating a latency of the server-side application;
• wherein estimating the latency of the server-side application comprises:
• for each service in the set of server-side services, identifying one or more application programming interfaces (APIs), of said each service, that the server-side application is configured to call;
• identifying a first API, of a first service, that the server-side application is configured to call;
• determining a first latency associated with the first API;
• identifying a second API, of a second service, that the server-side application is configured to call, wherein the second API is different than the first API;
• determining a second latency associated with the second API;
• applying a weight to the first latency based on a number of times the first API was previously called.