Coordinated microservices
Techniques are provided for a coordinated microservice system including a coordinator and multiple services, which interact with each other. Each of the services can have multiple execution instances, which run independently of each other. In operation, each instance of each service can use, or otherwise depend upon, one or more of the other services to perform at least some of its respective function(s). The coordinator monitors execution requests from each instance of the services to other services and calculates an available capacity of the other services upon which the requesting services depend to execute each of the execution requests based on the monitored performance metrics of the other services and level(s) of resource consumption associated with each of the execution requests. The coordinator then selects one of the execution requests based on the available capacity of the other services to service the execution requests without degrading the other services.
1. A method of coordinating execution among multiple instances of a service, the method comprising:
executing a plurality of services by a computing device, the plurality of services including at least a first service and second service;
monitoring a first execution request from a first instance of the first service, the first execution request being associated with a first level of resource consumption;
monitoring a second execution request from a second instance of the first service, the second execution request being associated with a second level of resource consumption;
calculating an available capacity of the second service to execute the first execution request and the second execution request based on a performance metric of the second service, the first level of resource consumption, and the second level of resource consumption;
selecting one of the first execution request and the second execution request based on the available capacity of the second service; and
improving execution performance of the first service and the second service executing on the computing device by causing one of the first instance of the first service to execute the first execution request and the second instance of the first service to execute the second execution request based on the selection of the first execution request and the second execution request;
wherein the first and second services are microapplications.
2. The method of claim 1 , wherein calculating the available capacity of the second service is further based on a performance metric of a third service from which the second service depends to execute the first execution request, the second execution request, or both.
3. The method of claim 1 , wherein causing the first instance of the first service to execute the first execution request includes sending a first coordination command to the second instance of the first service, wherein causing the second instance of the first service to execute the second execution request includes sending a second coordination command to the first instance of the first service, and wherein the first coordination command and the second coordination command each include a command to postpone the second execution request and the first execution request, respectively.
4. The method of claim 1 , further comprising receiving, via a proxy associated with the second service, the performance metric associated with the second service; and storing the performance metric associated with the second service in a datastore prior to calculating the available capacity of the second service to execute the first execution request and the second execution request.
5. The method of claim 4 , wherein the performance metric is received at a periodic interval or in response to a request to get the performance metric from the second service.
6. The method of claim 1 , further comprising applying a pre-defined rule to the performance metric of the second service to determine whether an event has occurred, wherein one of the first execution request and the second execution request is selected based on a determination that the event has occurred.
7. The method of claim 6 , wherein the performance metric of the second service is a first performance metric, wherein the pre-defined rule is a first rule, and wherein the method further comprises applying a second pre-defined rule to a second performance metric of the second service to determine whether the event is verified, and wherein one of the first execution request and the second execution request is selected based on a determination that the event is verified.
8. A computer program product including one or more non-transitory machine-readable mediums having instructions encoded thereon that when executed by at least one processor cause a process to be carried out, the process comprising:
executing a plurality of services by a computing device, the plurality of services including at least a first service and second service;
monitoring a first execution request from a first instance of the first service, the first execution request being associated with a first level of resource consumption;
monitoring a second execution request from a second instance of the first service, the second execution request being associated with a second level of resource consumption;
calculating an available capacity of the second service to execute the first execution request and the second execution request based on a performance metric of the second service, the first level of resource consumption, and the second level of resource consumption;
selecting one of the first execution request and the second execution request based on the available capacity of the second service; and
improving execution performance of the first service and the second service executing on the computing device by causing one of the first instance of the first service to execute the first execution request and the second instance of the first service to execute the second execution request based on the selection of the first execution request and the second execution request.
9. The computer program product of claim 8 , wherein calculating the available capacity of the second service is further based on a performance metric of a third service from which the second service depends upon to execute the first execution request and/or the second execution request.
10. The computer program product of claim 8 , wherein causing the first instance of the first service to execute the first execution request includes sending a first coordination command to the second instance of the first service, wherein causing the second instance of the first service to execute the second execution request includes sending a second coordination command to the first instance of the first service, and wherein the first coordination command and the second coordination command each include a command to postpone or delay the second execution request and the first execution request, respectively.
11. The computer program product of claim 8 , the process further comprising receiving, via a proxy associated with the second service, the performance metric associated with the second service; and storing the performance metric associated with the second service in a datastore prior to calculating the available capacity of the second service to execute the first execution request and the second execution request.
12. The computer program product of claim 11 , wherein the performance metric is received at a periodic interval or in response to a request to get the performance metric from the second service.
13. The computer program product of claim 8 , the process further comprising applying a pre-defined rule to the performance metric of the second service to determine whether an event has occurred, wherein one of the first execution request and the second execution request is selected based on a determination that the event has occurred.
14. The computer program product of claim 13 , wherein the performance metric of the second service is a first performance metric, wherein the pre-defined rule is a first rule, and wherein the process further comprises applying a second pre-defined rule to a second performance metric of the second service to determine whether the event is verified, and wherein one of the first execution request and the second execution request is selected based on a determination that the event is verified.
15. A system comprising:
a storage; and
at least one processor operatively coupled to the storage, the at least one processor configured to execute instructions stored in the storage that when executed cause the at least one processor to carry out a process including:
executing a plurality of services by a computing device, the plurality of services including at least a first service and second service;
monitoring a first execution request from a first instance of the first service, the first execution request being associated with a first level of resource consumption;
monitoring a second execution request from a second instance of the first service, the second execution request being associated with a second level of resource consumption;
calculating an available capacity of the second service to execute the first execution request and the second execution request based on a performance metric of the second service, the first level of resource consumption, and the second level of resource consumption;
selecting one of the first execution request and the second execution request based on the available capacity of the second service; and
improving execution performance of the first service and the second service executing on the computing device by causing one of the first instance of the first service to execute the first execution request and the second instance of the first service to execute the second execution request based on the selection of the first execution request and the second execution request.
16. The system of claim 15 , wherein calculating the available capacity of the second service is further based on a performance metric of a third service from which the second service depends upon to execute the first execution request and/or the second execution request.
17. The system of claim 15 , wherein causing the first instance of the first service to execute the first execution request includes sending a first coordination command to the second instance of the first service, wherein causing the second instance of the first service to execute the second execution request includes sending a second coordination command to the first instance of the first service, and wherein the first coordination command and the second coordination command each include a command to postpone or delay the second execution request and the first execution request, respectively.
18. The system of claim 15 , the process further comprising receiving, via a proxy associated with the second service, the performance metric associated with the second service; and
storing the performance metric associated with the second service in a datastore prior to calculating the available capacity of the second service to execute the first execution request and the second execution request.
19. The system of claim 15 , the process further comprising applying a pre-defined rule to the performance metric of the second service to determine whether an event has occurred, wherein one of the first execution request and the second execution request is selected based on a determination that the event has occurred.
20. The system of claim 19 , wherein the performance metric of the second service is a first performance metric, wherein the pre-defined rule is a first rule, and wherein the process further comprises applying a second pre-defined rule to a second performance metric of the second service to determine whether the event is verified, and wherein one of the first execution request and the second execution request is selected based on a determination that the event is verified.