Configuration hash comparison
Disclosed embodiments are directed at systems, methods, and architecture for operating a control plane of a microservice architecture application. The control plane may link a plurality of APIs for the microservice architecture application. The communication between the APIs and the control plane enables the control plane to assess the settings of the APIs compared to stored versions of the settings. The settings and stored versions may each be hashed with a hashing algorithm. The control plane may instruct APIS to update their settings responsive to determining that the settings do not match the stored versions.
1. A method comprising:
accessing, by a control plane, a deployed version of configurable settings associated with a first microservice as stored with the control plane;
comparing current settings received from the first microservice to the deployed version of the configurable settings of the first microservice; and
responsive to the received current settings not matching the deployed version, moving a process from the first microservice to a second microservice.
2. The method of claim 1 , wherein the second microservice includes a data plane proxy configured to communicate with the control plane.
3. The method of claim 2 , further comprising:
receiving the current settings from the data plane proxy of the second microservice; and
responsive to the received current settings of the second microservice not matching the deployed version associated with the first microservice, instructing the data plane proxy to update the current settings of the second microservice to match the deployed version associated with the first microservice.
4. The method of claim 3 , further comprising:
hashing the current settings of the second microservice and the deployed version associated with the first microservice prior to determining that the received current settings of the second microservice do not match the deployed version.
5. The method of claim 2 , wherein the data plane proxy of the second microservice runs simultaneously with the second microservice.
6. The method of claim 1 , further comprising:
receiving an output of the first microservice, wherein the first microservice is one of a plurality of microservices, each microservice in the plurality configured to perform the process and produce output data based on the process;
determining that the output of the first microservice is outside of an expected range of values, wherein each output data from the plurality of microservices is within the expected range; and
responsive to the determination, requesting current settings of the first microservice.
7. The method of claim 1 , further comprising:
comparing current settings of the second microservice to the deployed version associated with the first microservice; and
responsive to the current settings of the second microservice matching the deployed version associated with the first microservice, selecting the second microservice to move the process to.
8. The method of claim 1 , further comprising:
hashing the deployed version of the configurable settings using a hashing algorithm, wherein the received current settings were hashed using the hashing algorithm; and
comparing the hashed deployed version to the received current settings.
9. The method of claim 1 , wherein the current settings are received from the first microservice responsive to determining, by the control plane, the first microservice is outputting values outside of an expected range at a threshold frequency.
10. A method comprising:
receiving, from a data plane proxy associated with a first microservice, current settings of the first microservice;
accessing a deployed version of configurable settings for the first microservice from a database; and
responsive to the received current settings not matching the deployed version, sending instructions to the data plane proxy to move a process at the at the first microservice to a second microservice.
11. The method of claim 10 , wherein the data plane proxy runs simultaneously with the second microservice and communicates outputs from the second microservice to a control plane.
12. The method of claim 10 , further comprising:
hashing current settings of the second microservice were hashed prior to being sent to a control plane by the data plane proxy; and
comparing the hashed current settings of the second microservice to the deployed version of the configurable settings associated with the first microservice, wherein the deployed version comprises a hashed estimate of the current settings of the first microservice stored by the control plane.
13. The method of claim 12 , wherein the control plane is configured to communicate information about the second microservice to a computing device running a microservice architecture application.
14. The method of claim 12 , further comprising:
receiving an output of the first microservice, wherein the first microservice is one of a plurality of microservices, each microservice in the plurality configured to perform the process and produce output data based on the process;
determining that the output of the first microservice is outside of an expected range of values, wherein each output data from the plurality of microservices is within the expected range; and
responsive to the determination, requesting current settings of the first microservice from the data plane proxy.
15. The method of claim 10 , further comprising:
hashing the deployed version of the current settings using a hashing algorithm, wherein the received current settings were hashed using the hashing algorithm.
16. The method of claim 10 , wherein receiving the current settings of the first microservice is responsive to determining, by a control plane, the first microservice is outputting values outside of an expected range at a threshold frequency.
17. A system comprising:
a computer processor; and
a non-transitory computer-readable storage medium storing instructions that when executed cause the computer processor to perform actions comprising:
accessing a deployed version of configurable settings for a first microservice from a database;
comparing current settings as received from a proxy of the first microservice to the deployed version of the configurable settings; and
responsive to the received current settings not matching the deployed version, moving a process at the at the first microservice to a second microservice.
18. The system of claim 17 , the actions further comprising:
receiving an output of the first microservice, wherein the first microservice is one of a plurality of microservices, each microservice in the plurality configured to perform the process and produce output data based on the process;
determining that the output of the first microservice is outside of an expected range of values, wherein each output data from the plurality of microservices is within the expected range; and
responsive to the determination, requesting current settings of the first microservice.
19. The system of claim 17 , the actions further comprising:
receiving, from a computing device communicatively connected to a control plane configured to communicate information about the second microservice to the computing device, a request for the current settings of the second microservice.
20. The system of claim 19 , wherein the computing device is connected to the control plane via a network.