Systems and methods for real-time configurable load determination
First Claim
Patent Images
1. A method of performing a security service comprising:
- receiving network data at each of a hierarchy of microservices including, at a lowest level, an interface microservice to receive network data, each of the microservices to run on a processor core and to attempt to determine the most efficiently usable higher-level microservice to which to transfer processed data, the determination being made without requiring knowledge of impending processing requirements of the higher-level microservice, and instead by accessing a load table containing temporally relevant and scaled loading metrics generated by and received from higher-level microservices in prior responses; and
processing received network data by each microservice by performing a security service on data included with a request, calculating a service load associated with and during the performing the security service, and transmitting a response including the service load.
4 Assignments
0 Petitions
Accused Products
Abstract
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.
20 Citations
20 Claims
-
1. A method of performing a security service comprising:
-
receiving network data at each of a hierarchy of microservices including, at a lowest level, an interface microservice to receive network data, each of the microservices to run on a processor core and to attempt to determine the most efficiently usable higher-level microservice to which to transfer processed data, the determination being made without requiring knowledge of impending processing requirements of the higher-level microservice, and instead by accessing a load table containing temporally relevant and scaled loading metrics generated by and received from higher-level microservices in prior responses; and processing received network data by each microservice by performing a security service on data included with a request, calculating a service load associated with and during the performing the security service, and transmitting a response including the service load. - View Dependent Claims (2, 3, 4, 5, 6, 7)
-
-
8. A system to perform a security service comprising:
-
a hierarchy of microservices including, at a lowest level, an interface microservice to receive network data, each of the microservices to run on a processor core and to attempt to determine the most efficiently usable higher-level microservice to which to transfer processed data, the determination to be made without requiring knowledge of impending processing requirements of the higher-level microservice, and instead by accessing a load table containing temporally relevant and scaled loading metrics generated by and received from higher-level microservices in prior responses; and each microservice to process received network data by performing a security service on data included with a request, calculating a service load associated with and during the performing the security service, and transmitting a response to the request, the response to include the service load. - View Dependent Claims (9, 10, 11, 12, 13, 14)
-
-
15. A non-transitory computer-readable medium containing computer-executable instructions to which a system to perform a security service is to respond by:
-
receiving network data at each of a hierarchy of microservices including, at a lowest level, an interface microservice to receive network data, each of the microservices to run on a processor core and to attempt to determine the most efficiently usable higher-level microservice to which to transfer processed data, the determination being made without requiring knowledge of impending processing requirements of the higher-level microservice, and instead by accessing a load table containing temporally relevant and scaled loading metrics generated by and received from higher-level microservices in prior responses; and processing received network data by each microservice by performing a security service on data included with a request, calculating a service load associated with and during the performing the security service, and transmitting a response including the service load. - View Dependent Claims (16, 17, 18, 19, 20)
-
Specification