Service management method and the device
The present invention provides a method and a device for service management, wherein the method comprises: detecting popularity of use of a remote target service by an application; and when the popularity reaches a first threshold value, loading the target service to the application locally. The present invention improves the response efficiency and adaptive capability of a distributed system.
1. A method for service management, comprising:
invoking, by a first application in a first device, a remote target service stored on a second device and associated with a second application in the second device, wherein the remote target service is provided by the second device through a network to the first device;
detecting, by the first device, popularity of use of the remote target service by the first application, wherein the popularity of use of the remote target service comprises a frequency of use of the remote target service by the first application;
determining, by the first device, that the remote target service meets a plurality of migration conditions, wherein the migration conditions comprise:
that the first device locally comprises a data source required by the remote target service,
that the remote target service is an independent service that does not have mutual dependence with any other service on the second device, and
that the remote target service is a stateless service; and
when the popularity reaches a first threshold value, loading, by the first device, a copy of the remote target service to the first device to be local with the first application, wherein:
the determining that the remote target service meets a plurality of migration conditions is requisite for the loading,
the loading comprises loading a copy of a segment of a logic component of the remote target service and excludes loading a data component of the remote target service, and
the remote target service remains available on the second device and local with the second application after the loading.
2. The method of claim 1 , wherein, after the loading the copy of the remote target service to be local with the first application, the method further comprises:
unloading, by the first device, the copy of the remote target service from being local with the first application when the popularity reaches a second threshold value.
3. The method of claim 1 , wherein, after the loading the copy of the remote target service to be local with the first application, the method further comprises:
unloading, by the first device, the copy of the remote target service from being local with the first application when it is determined that the remote target service is updated.
4. The method of claim 1 , wherein, after the loading the copy of the remote target service to be local with the first application, the method further comprises:
when executing the first application, determining, by the first device, whether the first application has the copy of the remote target service locally; and
if the determination result is that the copy of the remote target service is local, using, by the first device, the copy of the remote target service to execute the first application.
5. The method of claim 1 , wherein the use of the remote target service requires accessing a remote data source by the first application before and after the loading the copy of the remote target service to be local with the first application.
6. The method of claim 1 , wherein the data source required by the remote target service is implemented separately from the first application on the first device.
7. A first device for service management, comprising one or more processors and one or more non-transitory computer-readable memories coupled to the one or more processors and configured with instructions executable by the one or more processors to cause the first device to perform operations comprising:
invoking, by a first application in the first device, a remote target service stored on a second device and associated with a second application in the second device, wherein the remote target service is provided by the second device through a network to the first device;
detecting popularity of use of the remote target service by the first application, wherein the popularity of use of the remote target service comprises a frequency of use of the remote target service by the first application;
determining that the remote target service meets a plurality of migration conditions, wherein the migration conditions comprise:
that the first device locally comprises a data source required by the remote target service,
that the remote target service is an independent service that does not have mutual dependence with any other service on the second device, and
that the remote target service is a stateless service; and
when the popularity reaches a first threshold value, loading a copy of the remote target service to the first device to be local with the first application, wherein:
the determining that the remote target service meets a plurality of migration conditions is requisite for the loading,
the loading comprises loading a copy of a segment of a logic component of the remote target service and excludes loading a data component of the remote target service, and
the remote target service remains available on the second device and local with the second application after the loading.
8. The device of claim 7 , wherein the operations further comprise:
unloading the remote target service from being local with the first application when the popularity reaches a second threshold value.
9. The device of claim 7 , wherein the operations further comprise:
monitoring updates to the remote target service; and
unloading the copy of the remote target service from being local with the first application when it is determined that the remote target service is updated.
10. The device of claim 7 , wherein the operations further comprise:
determining, when executing the first application, whether the first application has the copy of the remote target service locally; and
if the determination result is that the copy of the remote target service is local, use the copy of the remote target service to execute the first application.
11. The device of claim 7 , wherein the use of the remote target service requires accessing a remote data source by the first application before and after the loading the copy of the remote target service to be local with the first application.
12. The device of claim 7 , wherein the data source required by the remote target service is implemented separately from the first application on the first device.
13. A non-transitory computer-readable storage medium storing instructions that, when executed by a processor of a first device, cause the processor to perform operations comprising:
invoking, by a first application in the first device, a remote target service stored on a second device and associated with a second application in the second device, wherein the remote target service is provided by the second device through a network to the first device;
detecting popularity of use of the remote target service by the first application, wherein the popularity of use of the remote target service comprises a frequency of use of the remote target service by the first application;
determining that the remote target service meets a plurality of migration conditions, wherein the migration conditions comprise:
that the first device locally comprises a data source required by the remote target service,
that the remote target service is an independent service that does not have mutual dependence with any other service on the second device, and
that the remote target service is a stateless service; and
when the popularity reaches a first threshold value, loading a copy of the remote target service to the first device to be local with the first application, wherein:
the determining that the remote target service meets a plurality of migration conditions is requisite for the loading,
the loading comprises loading a copy of a segment of a logic component of the remote target service and excludes loading a data component of the remote target service, and
the remote target service remains available on the second device and local with the second application after the loading.
14. The non-transitory computer-readable storage medium of claim 13 , wherein, after the loading the copy of the remote target service to be local with the first application, the operations further comprise:
unloading the copy of the remote target service from being local with the first application when the popularity reaches a second threshold value.
15. The non-transitory computer-readable storage medium of claim 13 , wherein, after the loading the copy of the remote target service to be local with the first application, the operations further comprise:
unloading the copy of the remote target service from being local with the first application when it is determined that the remote target service is updated.
16. The non-transitory computer-readable storage medium of claim 13 , wherein, after the loading the copy of the remote target service to be local with the first application, the operations further comprise:
when executing the first application, determining whether the first application has the copy of the remote target service locally;
if the determination result is that the copy of the remote target service is local, using the copy of the remote target service to execute the first application.
17. The non-transitory computer-readable storage medium of claim 13 , wherein the use of the remote target service requires accessing a remote data source by the first application before and after the loading the copy of the remote target service to be local with the first application.
18. The non-transitory computer-readable storage medium of claim 13 , wherein the data source required by the remote target service is implemented separately from the first application on the first device.