Systems and methods for real-time configurable load determination
Systems and methods are described herein generally relating to network security, and in particular, embodiments described generally relate to real-time configurable load determination. For example, a method is disclosed, which calls for receiving a request to perform a security service, performing the security service on data included with the request; calculating a service load associated with and during the performing the security service, and transmitting a response to the request, wherein the response includes the calculated service load.
1. A method comprising:
receiving a request to perform a security service by a hierarchy of microservices, each microservice to run on a processor core and to attempt to determine, by accessing a load table containing temporally relevant and scaled loading metrics generated by and received from higher-level microservices in prior responses, the most, efficiently usable higher-level microservice to which to transfer processed data;
performing the security service on data included with the request;
calculating a service load associated with and while performing the security service; and
transmitting a response to the request, the response including the service load.
2. The method of claim 1 , wherein the service load comprises a first property value selected from a group consisting of processor utilization, memory utilization, disk capacity, disk throughput, input/output throughput, and event throughput.
3. The method of claim 1 , wherein the loading metrics are based on processor utilization and memory utilization of the higher level microservices.
4. The method of claim 1 , wherein each microservice, before attempting to determine the most efficiently usable higher-level microservice to which to transfer processed data, is to request a current service load from one or more higher-level microservices by transmitting a null request to the higher-level microservice.
5. The method of claim 1 , wherein each of the microservices maintains and uses its own load table on its own processor core.
6. The method of claim 1 , wherein the load table is maintained in a global memory and made available to lower-level microservices.
7. The method of claim 1 , wherein the scaled loading metrics generated by and received from higher-level microservices in prior responses each comprise a handle to obtain calculated load values from a service available to lower-level microservices.
8. A system comprising:
a hierarchy of microservices to receive a request to perform a security service, each microservice, running on a processor core, to:
access a load table containing temporally relevant and scaled loading metrics generated by and received from higher-level microservices in prior responses to determine, independent of impending processing requirements of the higher-level microservices, the most efficiently usable higher-level microservice to which to transfer processed data;
perform the security service on data included with the request;
calculate a service load associated with and while performing the security service; and
transmit a response to the request, the response including the service load.
9. The system of claim 8 , wherein the service load comprises a first property value selected from a group consisting of processor utilization, memory utilization, disk capacity, disk throughput, input/output throughput, and event throughput.
10. The system of claim 8 , wherein the loading metrics are based on processor utilization and memory utilization of the higher level microservices.
11. The system of claim 8 , wherein each microservice, before attempting to determine the most efficiently usable higher-level microservice to which to transfer processed data, is to request a current service load from one or more higher-level microservices by transmitting a null request to the higher-level microservice.
12. The system of claim 8 , wherein each of the microservices maintains and uses its own load table on its own processor core.
13. The system of claim 8 , wherein the load table is maintained in a global memory and made available to lower-level microservices.
14. The system of claim 8 , wherein the temporally relevant and scaled loading metrics generated by and received from higher-level microservices in prior responses each comprise a handle to obtain calculated load values from a service available to lower-level microservices.
15. A non-transitory computer-readable medium containing computer-executable instructions to which a hierarchy of microservices is to respond by:
receiving a request to perform a security service at a hierarchy of microservices, each microservice to run on a processor core and to attempt to determine, by accessing a load table containing temporally relevant and scaled loading metrics generated by and received from higher-level microservices in prior responses, the most efficiently usable higher-level microservice to which to transfer processed data;
performing the security service on data included with the request;
calculating a service load associated with and while performing the security service; and
transmitting a response to the request, the response including the service load.
16. The non-transitory computer-readable medium of claim 15 , wherein the service load comprises a first property value selected from a group consisting of processor utilization, memory utilization, disk capacity, disk throughput, input/output throughput, and event throughput.
17. The non-transitory computer-readable medium of claim 15 , wherein the loading metrics are based on processor utilization and memory utilization of the higher level microservices.
18. The non-transitory computer-readable medium of claim 15 , wherein each microservice, before attempting to determine the most efficiently usable higher-level microservice to which to transfer processed data, is to request a current service load from one or more higher-level microservices by transmitting a null request to the higher-level microservice.
19. The non-transitory computer-readable medium of claim 15 , wherein either a separate version of the load table is maintained by each of the microservices, or the load table is maintained in a global memory and made available to lower-level microservices.
20. The non-transitory computer-readable medium of claim 15 , wherein the scaled loading metrics generated by and received from higher-level microservices in prior responses each comprise a handle to obtain calculated load values from a service available to lower-level microservices.