Global optimization of a service-oriented system
US-10182129-B1 · Jan 15, 2019 · US
US11399072B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-11399072-B2 |
| Application number | US-202117196800-A |
| Country | US |
| Kind code | B2 |
| Filing date | Mar 9, 2021 |
| Priority date | Jul 31, 2018 |
| Publication date | Jul 26, 2022 |
| Grant date | Jul 26, 2022 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
In some aspects, a non-transitory computer-readable storage medium having computer-executable instructions stored thereon that, upon execution by a processor, causes the processor to receive an indicator of a functionality; map the indicator to a first service and a second service dependent on the first service; identify a policy based on the first service and the second service; and determine, based on the policy, locations of deployment for the first service and the second service.
Opening claim text (preview).
What is claimed is: 1. A non-transitory computer-readable storage medium having computer-executable instructions stored thereon that, upon execution by a processor, cause the processor to: receive an indicator of a functionality; map the indicator to a first service and a second service; identify a policy based on the first service and the second service, wherein the policy is used to determine a location of deployment based on whether a dependency exists between the first service and the second service, wherein the policy is associated with a cluster of hosts, wherein the policy is used to determine whether to deploy the first service and the second service on a same cluster of hosts or on different clusters of hosts; and determine, based on the policy, a first location of deployment for the first service and a second location of deployment of the second service. 2. The medium of claim 1 , wherein the policy is used to determine whether to deploy the first service and the second service on a same virtual machine or on different virtual machines. 3. The medium of claim 1 , wherein the policy is used to determine the first location of deployment and the second location of deployment at least based on whether there are dependencies between the first service and the second service. 4. The medium of claim 1 , wherein the policy is used to determine the first location of deployment and the second location of deployment at least based on system variables. 5. The medium of claim 4 , wherein the system variables include one or more of license keys, feature flags, resource limitations, or hardware configurations. 6. The medium of claim 1 , wherein the policy is updated in response to a license update. 7. The medium of claim 1 , wherein the location of deployment includes two different virtual machines on different clusters of host machines. 8. The medium of claim 1 , wherein the first location of deployment and the second location of deployment is a common virtual machine. 9. The medium of claim 1 , wherein the policy is used to determine whether to deploy the first service and the second service on a same host or on different hosts. 10. An apparatus, comprising a processor and a memory, wherein the memory includes programmed instructions that, when executed by the processor, cause the apparatus to: receive an indicator of a functionality; map the indicator to a first service and a second service; identify a policy based on the first service and the second service, wherein the policy is used to determine a first location of deployment and a second location of deployment based on whether a dependency exists between the first service and the second service, wherein the policy is associated with a cluster of hosts, wherein the policy is used to determine whether to deploy the first service and the second service on a same cluster of hosts or on different clusters of hosts; and determine, based on the policy, locations of deployment for the first service and the second service. 11. The apparatus of claim 10 , wherein the policy is used to determine whether to deploy the first service and the second service on a same virtual machine or on different virtual machines. 12. The apparatus of claim 10 , wherein the policy is used to determine the first location of deployment and the second location of deployment at least based on whether there are dependencies between the first service and the second service. 13. The apparatus of claim 10 , wherein the policy is used to determine the first location of deployment and the second location of deployment at least based on system variables. 14. The apparatus of claim 13 , wherein the system variables include one or more of license keys, feature flags, resource limitations, or hardware configurations. 15. The apparatus of claim 10 , wherein the policy is updated in response to a license update. 16. The apparatus of claim 10 , wherein the first location of deployment and the second location of deployment includes two different virtual machines on different clusters of host machines. 17. The apparatus of claim 10 , wherein the first location of deployment and the second location of deployment is a common virtual machine. 18. The apparatus of claim 10 , wherein the policy is used to determine whether to deploy the first service and the second service on a same host or on different hosts. 19. A computer-implemented method comprising: receiving an indicator of a functionality; map the indicator to a first service and a second service; identify a policy based on the first service and the second service, wherein the policy is used to determine a location of deployment based on whether a dependency exists between the first service and the second service, wherein the policy is associated with a cluster of hosts, wherein the policy is used to determine whether to deploy the first service and the second service on a same cluster of hosts or on different clusters of hosts; and determining, based on the policy, a first location of deployment and a second location of deployment for the first service and the second service. 20. The method of claim 19 , wherein the policy is used to determine whether to deploy the first service and the second service on a same virtual machine or on different virtual machines. 21. The method of claim 19 , wherein the policy is used to determine the first location of deployment and the second location of deployment at least based on whether there are dependencies between the first service and the second service. 22. The method of claim 15 , wherein the policy is used to determine the first location of deployment and the second location of deployment at least based on system variables. 23. The method of claim 22 , wherein the system variables include one or more of license keys, feature flags, resource limitations, or hardware configurations. 24. The method of claim 19 , wherein the first location of deployment and the second location of deployment includes two different virtual machines on different clusters of host machines. 25. The method of claim 19 , wherein the first location of deployment and the second location of deployment is a common virtual machine. 26. The method of claim 19 , wherein the policy is used to determine whether to deploy the first service and the second service on a same host or on different hosts.
Logical partitioning of resources; Management or configuration of virtualized resources (specific details on emulation or internal functioning of virtual machines G06F9/455) · CPC title
Service on demand, e.g. definition and deployment of services in real time · CPC title
Software deployment · CPC title
Energy efficient computing, e.g. low power processors, power management or thermal management · CPC title
based on client or server locations · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.