Dynamic, load-based, auto-scaling network security microservices architecture
System, methods, and apparatuses used to monitor network traffic of a datacenter and report security threats are described. For example, one embodiment selects a first microservice of a first hierarchy, configures the microservices of a second lower-level hierarchy to remove the first microservice from load balancing decisions to the first hierarchy, moves the first microservice to another server, configures data plane connectivity to the first microservice to reflect a change in server, and configures the microservices of the second hierarchy to include the first microservice in load balancing decisions to the first hierarchy.
1. A computer-implemented method comprising:
selecting a first security microservice of a first level of a hierarchy of security microservices;
configuring security microservices of a second lower-level of the hierarchy of security microservices to remove the first security microservice from load balancing decisions to the first level of the hierarchy of security microservices;
moving the first security microservice to another server;
configuring data plane connectivity to the first security microservice to reflect a change in servers;
configuring the security microservices of the second lower-level of the hierarchy of security microservices to include the first security microservice in load balancing decisions to the second lower-level of the hierarchy of security microservices; and
processing a packet from a flow of packets with the first security microservice,
wherein each level of the hierarchy of security microservices performs a different security operation.
2. The computer-implemented method of claim 1 , wherein the first security microservice was created by an existing microservice.
3. The computer-implemented method of claim 2 , wherein the existing microservice is a configuration microservice.
4. The computer-implemented method of claim 2 , wherein the first security microservice and the security microservices of the second lower-level hierarchy of security microservices communicate over a backplane.
5. The computer-implemented method of claim 4 , wherein the first security microservice is configured to use the backplane.
6. The computer-implemented method of claim 5 , wherein there exists, prior to the moving of the first security microservice to another server, a security microservice of the same hierarchy level as the first security microservice.
7. The computer-implemented method of claim 1 , wherein the load balancing decision utilizes information from security microservices of a higher-level hierarchy than the first hierarchy of security microservices.
8. The computer-implemented method of claim 7 , wherein data plane connectivity is configured through communication on a backplane.
9. The computer-implemented method of claim 1 , wherein a backplane and data plane comprise a managed network.
10. A non-transitory computer-readable medium storing instructions, which when executed by a hardware processor cause the processor to perform a method, the method comprising:
selecting a first security microservice of a first level of a hierarchy of security microservices;
configuring security microservices of a second lower-level of the hierarchy of security microservices to remove the first security microservice from load balancing decisions to the first level of the hierarchy of security microservices;
moving the first security microservice to another server;
configuring data plane connectivity to the first security microservice to reflect a change in servers;
configuring the security microservices of the second lower-level of the hierarchy of security microservices to include the first security microservice in load balancing decisions to the second lower-level of the hierarchy of security microservices; and
processing a packet from a flow of packets with the first security microservice,
wherein each level of the hierarchy of security microservices performs a different security operation.
11. The non-transitory computer-readable medium of claim 10 , wherein the first security microservice was created by an existing microservice.
12. The non-transitory computer-readable medium of claim 11 , wherein the existing microservice is a configuration microservice.
13. The non-transitory computer-readable medium of claim 11 , wherein the first security microservice and the security microservices of the second lower-level hierarchy of security microservices communicate over a backplane.
14. The non-transitory computer-readable medium of claim 13 , wherein the first security microservice is configured to use the backplane.
15. The non-transitory computer-readable medium of claim 14 , wherein there exists, prior to the moving of the first security microservice to another server, a microservice of the same hierarchy level as the first security microservice.
16. The non-transitory computer-readable medium of claim 10 , wherein the load balancing decision utilizes information from microservices of a higher-level hierarchy than the first hierarchy of security microservices.
17. The non-transitory computer-readable medium of claim 16 , wherein data plane connectivity is configured through communication on a backplane.
18. An apparatus comprising:
a hardware processor to execute instructions; and
memory coupled to the processor, the memory to store instructions which when executed by the processor cause:
selecting a first security microservice of a first level of a hierarchy of security microservices;
configuring security microservices of a second lower-level of the hierarchy of security microservices to remove the first security microservice from load balancing decisions to the first level of the hierarchy of security microservices;
moving the first security microservice to another server;
configuring data plane connectivity to the first security microservice to reflect a change in servers;
configuring the security microservices of the second lower-level of the hierarchy of security microservices to include the first security microservice in load balancing decisions to the second lower-level of the hierarchy of security microservices; and
processing a packet from a flow of packets with the first security microservice,
wherein each level of the hierarchy of security microservices performs a different security operation.
19. The apparatus of claim 18 ,
wherein the first security microservice was created by an existing microservice, the existing microservice being a configuration microservice.
20. The apparatus of claim 18 ,
wherein the first security microservice and the microservices of the second lower-level hierarchy of security microservices communicate over a backplane, and wherein the first security microservice is configured to use the backplane.