Deployment of services with dependencies
Metadata includes runtime dependencies for services that form an application. Each runtime dependency includes one or more of the one or more services, unless it has no runtime dependencies. A first of the services is selected, based on the metadata, that does not have runtime dependencies or those runtime dependencies are operational. The selected service is started. Other embodiments are described and claimed.
1. A method, performed by a management service running on a computing device, comprising:
receiving a metadata that declares runtime dependencies for each of one or more services, wherein each runtime dependency is another one of the one or more services and wherein the metadata includes a deployment queue that indicates a runtime dependency graph of the one or more services;
selecting, based on the metadata, a first of the one or more services that does not have runtime dependencies or the runtime dependencies are operational;
starting the first of the one or more services to deploy the one or more services, including popping the first of the one or more services off of the deployment queue to indicate the starting of the first of the one or more services;
querying the first of the one or more services to determine if the first of the one or more services is operational;
in response to the first of the one or more services not being operational, waiting for the first of the one or more services to become operational; and
in response to the first of the one or more services being operational, adding to the deployment queue, those of the one or more services that depend on the first of the one or more services, and selecting and starting a second of the one or more services to deploy the one or more second services including popping the second of the one or more services off of the deployment queue in accordance with the runtime dependency graph to indicate the starting of the second of the one or more services.
2. The method of claim 1 , wherein the second of the one or more services is selected such that it does not have any runtime dependencies or those runtime dependencies are operational.
3. The method of claim 2 , wherein determining that the first service is operational includes receiving a response from the first service that it is operational.
4. The method of claim 1 , wherein the metadata includes a data structure that represents a runtime dependency graph of the one or more services.
5. The method of claim 4 , wherein the data structure stores, for each of the one or more services, a service identifier as a key, and the runtime dependencies of the respective one or more services as a set of values.
6. The method of claim 1 , comprising selecting and starting each of the one or more services until all of the one or more services are operational, the one or more services being selected in a topological ordering.
7. The method of claim 1 , wherein the one or more services are one or more microservices that run in a containerized environment.
8. A non-transitory computer-readable medium storing instructions which, when executed by one or more processors of a networked computing device, cause the computing device to perform operations comprising:
receiving a metadata that declares runtime dependencies for each of one or more services, wherein each runtime dependency is another one of the one or more services and wherein the metadata includes a deployment queue that indicates a runtime dependency graph of the one or more services;
selecting, based on the metadata, a first of the one or more services that does not have runtime dependencies or the runtime dependencies are operational;
starting the first of the one or more services to deploy the one or more services, including popping the first of the one or more services off of the deployment queue to indicate the starting of the first of the one or more services;
querying the first of the one or more services to determine if the first of the one or more services is operational;
in response to the first of the one or more services not being operational, waiting for the first of the one or more services to become operational; and
in response to the first of the one or more services being operational, adding to the deployment queue, those of the one or more services that depend on the first of the one or more services, and selecting and starting a second of the one or more services to deploy the one or more second services including popping the second of the one or more services off of the deployment queue in accordance with the runtime dependency graph to indicate the starting of the second of the one or more services.
9. The non-transitory computer-readable medium of claim 8 , wherein the second of the one or more services is selected such that it does not have any runtime dependencies or those runtime dependencies are operational.
10. The non-transitory computer-readable medium of claim 9 , wherein determining that the first service is operational includes receiving a response from the first service that it is operational.
11. The non-transitory computer-readable medium of claim 8 , wherein the metadata includes a data structure that represents a runtime dependency graph of the one or more services.
12. The non-transitory computer-readable medium of claim 11 , wherein the data structure stores, for each of the one or more services, a service identifier as a key, and the runtime dependencies of the respective one or more services as a set of values.
13. The non-transitory computer-readable medium of claim 8 , comprising selecting and starting each of the one or more services until all of the one or more services are operational, the one or more services being selected in a topological ordering.
14. The non-transitory computer-readable medium of claim 8 , wherein the one or more services are one or more microservices that run in a containerized environment.
15. A data processing system, comprising:
computer-readable memory; and
a processor that executes instructions stored on the computer-readable memory, causing the data processing system to perform operations including:
receiving a metadata that declares runtime dependencies for each of one or more services, wherein each runtime dependency is another one of the one or more services and wherein the metadata includes a deployment queue that indicates a runtime dependency graph of the one or more services;
selecting, based on the metadata, a first of the one or more services that does not have runtime dependencies or the runtime dependencies are operational;
starting the first of the one or more services to deploy the first of the one or more services, including popping the first of the one or more services off of the deployment queue to indicate the starting of the first of the one or more services;
querying the first of the one or more services to determine if the first of the one or more services are operational;
in response to the first of the one or more services not being operational, waiting for the first of the one or more services to become operational; and
in response to the first of the one or more services being operational, adding to the deployment queue, those of the one or more services that depend on the first of the one or more services, and selecting and starting a second of the one or more services to deploy the one or more second services including popping the second of the one or more services off of the deployment queue in accordance with the runtime dependency graph to indicate the starting of the second of the one or more services.
16. The data processing system of claim 15 , wherein the second of the one or more services is selected such that it does not have any runtime dependencies or those runtime dependencies are operational.
17. The data processing system of claim 16 , wherein determining that the first service is operational includes receiving a response from the first service that it is operational.
18. The data processing system of claim 15 , wherein the metadata includes a data structure that represents a runtime dependency graph of the one or more services.
19. The data processing system of claim 18 , wherein the data structure stores, for each of the one or more services, a service identifier as a key, and the runtime dependencies of the respective one or more services as a set of values.
20. The data processing system of claim 15 , wherein the one or more services are one or more microservices that run in a containerized environment.