US20150081914A1 - Allocation of Resources Between Web Services in a Composite Service - Google Patents
Allocation of Resources Between Web Services in a Composite Service Download PDFInfo
- Publication number
- US20150081914A1 US20150081914A1 US14/491,059 US201414491059A US2015081914A1 US 20150081914 A1 US20150081914 A1 US 20150081914A1 US 201414491059 A US201414491059 A US 201414491059A US 2015081914 A1 US2015081914 A1 US 2015081914A1
- Authority
- US
- United States
- Prior art keywords
- web service
- sla
- resources
- service
- subscriber
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
- H04L47/24—Traffic characterised by specific attributes, e.g. priority or QoS
- H04L47/2425—Traffic characterised by specific attributes, e.g. priority or QoS for supporting services specification, e.g. SLA
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
- G06F9/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
- G06F9/5027—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals
- G06F9/5055—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals considering software capabilities, i.e. software resources associated or available to the machine
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/70—Admission control; Resource allocation
Definitions
- hosted services may be offered at various levels, including end user services and various backend services.
- a hosted service may offer one level of service to one hosted service and offer another level of service to another hosted service.
- the various levels of service may refer to different allocations of resources, such as processing resources, memory resources, networking resources, and/or the like. Combining these hosted services can yield a composite service. It is difficult, however, to integrate multiple levels of hosted services, especially when these hosted services are offered by different service providers.
- a composite service may include multiple web services, such as a first web service and a second web service.
- the second web service may utilize resources provided by the first web service.
- the second web service may subscribe to a level of service (e.g., the SLA type) from the first web service.
- the first web service may be referred to as the publisher web service
- the second web service may be referred to as the subscriber web service.
- the subscriber web service can send a request for information to the publisher web service.
- the request for information may include an identifier of the subscriber web service.
- the publisher web service may retrieve the SLA type associated with the identifier of the subscriber web service.
- the publisher web service may then allocate resources for satisfying the request for information based on the SLA type.
- the publisher web service may route the request for information to a server adapted to provide the information.
- the server can then provide the information directly to the subscriber web service in response to the request for information.
- the publisher web service may retrieve a uniform resource locator (URL) based on the SLA type.
- the URL may correspond to a server configured to provide the information.
- the subscriber web service can then access the URL in order to retrieve the information.
- URL uniform resource locator
- Example technologies may provide for allocating resources between web services in a composite service.
- the technologies receive a request for information from a subscriber web service.
- the request for information may include a SLA type between a publisher web service and the subscriber web service and an identifier of the subscriber web service.
- the composite service may include the publisher web service and the subscriber web service.
- the technologies retrieve a resource allocation associated with the SLA type.
- the technologies allocate a set of resources from multiple resources of the publisher web service to the subscriber web service according to the resource allocation and the identifier.
- the set of resources may be configured to satisfy the request for information.
- FIG. 1 is a block diagram illustrating a composite service adapted to allocate resources of a publisher web service to a subscriber web service according to the subscriber web service's SLA type, in accordance with some embodiment
- FIG. 2 is a flow diagram illustrating a method for allocating resources of a publisher web service to a subscriber web service according to the subscriber web service's SLA type, in accordance with some embodiments.
- FIG. 3 is a computer architecture diagram showing an illustrative computer hardware architecture for a computing system capable of implementing the embodiments presented herein.
- a composite service may include multiple web services. Each of these web services may be a publisher web service and/or a subscriber web service.
- a subscriber web service may refer to a web service that utilizes resources provided by a publisher web service.
- a subscriber web service may be associated with a SLA type corresponding to a particular publisher web service.
- a publisher web service may allocate resources for each corresponding subscriber web service depending on the subscriber web service's SLA type.
- program modules include routines, programs, components, data structures, and other types of structures that perform particular tasks or implement particular abstract data types.
- program modules include routines, programs, components, data structures, and other types of structures that perform particular tasks or implement particular abstract data types.
- program modules include routines, programs, components, data structures, and other types of structures that perform particular tasks or implement particular abstract data types.
- the subject matter described herein may be practiced with other computer system configurations, including hand-held devices, multiprocessor systems, microprocessor-based or programmable consumer electronics, minicomputers, mainframe computers, and the like.
- FIG. 1 illustrates a composite service 100 adapted to allocate resources of a publisher web service to a subscriber web service according to the subscriber web service's SLA type, in accordance with some embodiments.
- the composite service 100 may include a first web service 102 , a second web service 104 , and a third web service 106 .
- the web services 102 - 106 may be coupled via a communications network 108 .
- An example of the composite service 100 is the monitoring service described in U.S. patent application Ser. No. 12/900,481, filed Oct. 8, 2010, entitled “Providing a Monitoring Service in a Cloud-Based Computing Environment,” Attorney Docket No. 330467.01, which is hereby incorporated by reference in its entirety.
- Some examples of the web services 102 - 106 include the various web services (e.g., controller application, monitor application, finder application, analyzer application, notifier application, etc.) also described in the above referenced and incorporated patent application entitled “Providing a Monitoring Service in a Cloud-Based Environment.”
- the first web service 102 may include a SLA module 109 and resource allocation table 110 .
- the resource allocation table 110 may include a first resource allocation 111 A and a second resource allocation 111 B.
- the second web service 104 may include a request module 112 A and a SLA type 114 A.
- the third web service 106 may include a request module 112 B and a SLA type 114 B.
- the first web service 102 may be referred to as a publisher web service
- the second web service 104 and the third web service 106 may be referred to a subscriber web services. That is, the second web service 104 and the third web service 106 may be configured to utilize resources provided by the first web service 102 .
- the web services 102 - 106 may each be a publisher web service and/or a subscriber web service, according to various embodiments.
- the second web service 104 and the third web service 106 may be associated with different SLA types 114 A, 114 B and unique identifiers 116 A, 116 B.
- the SLA types 114 A, 114 B may be associated with one or more publisher web services, including the first web service 102 .
- the SLA types 114 A, 114 B may also be associated with different fees paid by an operator of the second web service 104 and an operator of the third web service 106 to an operator of the first web service 102 .
- the SLA types 114 A, 114 B may be shared with multiple publisher services.
- the SLA types 114 A, 114 B may be associated with only the first web service 102 , while other SLA types may be associated with other publisher web services.
- the SLA type 114 A may correspond to a “platinum” level SLA type
- the SLA type 114 B may correspond to a “silver” level SLA type.
- the platinum level may be associated with a higher allocation of resources than the silver level. It should be appreciated that the platinum level and silver level SLA types are merely illustrative, and other SLA types may be similarly utilized.
- the first web service 102 may be a search service.
- the request modules 112 A, 112 B may be configured to send a request for information to the SLA module 109 .
- the request for information may include queries, the corresponding SLA types 114 A, 114 B, and the identifiers 116 A, 116 B of the second web service 104 and the third web service 106 .
- the SLA module 109 may retrieve resource allocations 111 A, 111 B corresponding to the SLA types 114 A, 114 B from the resource allocation table 110 .
- the SLA type 114 A may correspond to the resource allocation 111 A
- the SLA type 114 B may correspond to the resource allocation 111 B.
- the SLA module 109 may then allocate resources for performing the search service to the second web service 104 and the third web service 106 according to the retrieved resource allocations 111 A, 111 B and the identifiers 116 A, 116 B. For example, the SLA module 109 may allocate a first set of resources from multiple resources in the first web service 102 to the second web service 104 . The SLA module 109 may also allocate a second set of resources from the multiple resources in the first web service 102 to the third web service 106 .
- the resource allocation table 110 may be stored in the memory of a computer operating the first web service 102 . In other embodiments, the resource allocation table 110 may be stored in an external database accessible by a computer operating the first web service 102 .
- the resources may refer to one or more entities that a publisher web service is capable of allocating to multiple subscriber web services. Such resources may be allocated according to suitable business rules associated with the various SLA types 114 A, 114 B.
- the resources may refer to servers adapted to retrieve search results corresponding to a query. For example, when the request module 112 A sends a query to the SLA module 109 , the SLA module 109 may allocate a dedicated server to the second web service 104 according to the platinum level. When the request module 112 B sends a query to the SLA module 109 , the SLA module 109 may allocate a shared server to the third web service 106 according to the silver level. The shared server may be shared by multiple web services.
- the SLA module 109 may allocate the dedicated server and the shared server by sending URLs corresponding to the dedicated server and the shared server to the request modules 112 A, 112 B.
- the second web service 104 and the third web service 106 can then utilize the URLs in order to retrieve the search results.
- the SLA module 109 may route the query directly to the dedicated server and the shared server.
- the dedicated server and the shared server can then retrieve and provide the search results to the second web service 104 and the third web service 106 without further action from the second web service 104 and the third web service 106 .
- the resources may refer to a level of access.
- the SLA module 109 may assign access to a greater number of search providers to the second web service 104 according to the platinum level.
- the SLA module 109 may assign a lesser number of search providers to the third web service 106 according to the silver level.
- the resources may refer to bandwidth or other suitable computer resources.
- the SLA module 109 may allocate additional computer resources to the second web service 104 according to the platinum level SLA.
- the SLA module 109 may decrease available computer resources available to the third web service 106 according to the silver level.
- the resources may refer to service availability or uptime.
- the SLA module 109 may allocate a greater time of availability or uptime to the second web service 104 according to the platinum level.
- the SLA module 109 may allocate a lesser time of availability or uptime to the third web service 106 according to the silver level.
- the resources may refer to a response time.
- the SLA module 109 may assign real-time or near real-time access of search results to the second web service 104 according to the platinum level.
- the SLA module 109 may assign delayed access to the third web service 106 according to the silver level.
- the SLA module 109 may allocate resources according to suitable business rules associated with the various SLA types 114 A, 114 B. These business rules may account for factors associated with the resources. In one example, where the SLA module 109 routes a query to a particular shared server, the SLA module 109 may account for current server load. In this example, the SLA module 109 may route the query to a shared server having the lowest current load. In another example, where the SLA module 109 routes a query to a particular server, the SLA module 109 may account for current server availability. In this example, the SLA module 109 may route the query to a server having current availability to respond to the query.
- the SLA module 109 may account for political requirements.
- the SLA module 109 may route the query to a server in China where business rules dictate that Chinese political requirements be met.
- FIG. 2 is a flow diagram illustrating a method for allocating resources of a publisher web service to a subscriber web service according to the subscriber web service's SLA type, in accordance with some embodiments.
- the logical operations described herein are implemented (1) as a sequence of computer implemented acts or program modules running on a computing system and/or (2) as interconnected machine logic circuits or circuit modules within the computing system. The implementation is a matter of choice dependent on the performance and other requirements of the computing system. Accordingly, the logical operations described herein are referred to variously as states operations, structural devices, acts, or modules.
- a routine 200 begins at operation 202 , where the SLA module 109 receives a request for information from a subscriber web service, such as the second web service 104 . That is, the request module 112 A may send the request for information to the SLA module 109 .
- the request for information may include the SLA type 114 A and the identifier 116 A.
- the SLA type 114 A may specify a level of service agreed between the second web service 104 and the first web service 102 .
- a higher fee paid by an operator of the second web service 104 to an operator of the first web service 102 may correspond to a higher level of service
- a lower fee paid by an operator of the second web service 104 to an operator of the first web service 102 may correspond to a lower level of service.
- the identifier 116 A may identify and/or specify a location of the second web service 104 .
- the SLA module 109 may retrieve a resource allocation associated with the SLA type 114 A.
- the SLA module 109 may retrieve the resource allocation 111 A corresponding to the SLA type 114 A from the resource allocation table 110 .
- the resource allocation table 110 may include multiple SLA types, each of which corresponds to a particular resource allocation. That is, different SLA types may correspond to different resource allocations.
- the routine 200 may proceed to operation 206 .
- the SLA module 109 allocates a set of resources of the first web service 102 to the second web service 104 according to the retrieved resource allocation 111 A and the identifier 116 A.
- the first web service 102 may include multiple resources. At least a portion of these resources may form the set of resources allocated to the first web service 102 .
- the SLA module 109 may determine the set of resources based on the retrieved resource allocation 111 A. The SLA module 109 may then allocate the set of resources to the second web service 104 as identified by the identifier 116 A.
- the routine 200 may repeat (e.g., periodically, continuously, or on demand as needed) or terminate.
- the computer 300 may include a central processing unit 302 , a system memory 304 , and a system bus 306 that couples the memory 304 to the 302 .
- the computer 300 may further include a mass storage device 312 for storing one or more program modules 314 and the database 316 . Examples of the program modules 314 may include the SLA module 109 and the request module 112 A.
- the database 316 may store the resource allocation table 110 .
- the mass storage device 312 may be connected to the processing unit 302 through a mass storage controller (not shown) connected to the bus 306 .
- the mass storage device 312 and its associated computer-storage media may provide non-volatile storage for the computer 300 .
- computer-storage media can be any available computer storage media that can be accessed by the computer 300 .
- computer-storage media may include volatile and non-volatile, removable and non-removable media implemented in any method or technology for the non-transitory storage of information such as computer-storage instructions, data structures, program modules, or other data.
- computer-storage media includes, but is not limited to, RAM, ROM, EPROM, EEPROM, flash memory or other solid state memory technology, CD-ROM, digital versatile disks (“DVD”), HD-DVD, BLU-RAY, or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by the computer 300 .
- the computer 300 may operate in a networked environment using logical connections to remote computers through a network such as the network 108 .
- the computer 300 may connect to the network 108 through a network interface unit 310 connected to the bus 306 .
- the network interface unit 310 may also be utilized to connect to other types of networks and remote computer systems.
- the computer 300 may also include an input/output controller 308 for receiving and processing input from a number of input devices (not shown), including a keyboard, a mouse, a microphone, and a game controller. Similarly, the input/output controller 308 may provide output to a display or other type of output device (not shown).
- the bus 306 may enable the processing unit 302 to read code and/or data to/from the mass storage device 312 or other computer-storage media.
- the computer-storage media may represent apparatus in the form of storage elements that are implemented using any suitable technology, including but not limited to semiconductors, magnetic materials, optics, or the like.
- the computer-storage media may represent memory components, whether characterized as RAM, ROM, flash, or other types of technology.
- the computer-storage media may also represent secondary storage, whether implemented as hard drives or otherwise. Hard drive implementations may be characterized as solid state, or may include rotating media storing magnetically-encoded information.
- the program modules 314 may include software instructions that, when loaded into the processing unit 302 and executed, cause the computer 300 to allocate resources of a publisher web service to a subscriber web service according to the subscriber web service's SLA type.
- the program modules 314 may also provide various tools or techniques by which the computer 300 may participate within the overall systems or operating environments using the components, flows, and data structures discussed throughout this description.
- the program modules 314 may implement interfaces for allocating resources of a publisher web service to a subscriber web service according to the subscriber web service's SLA type.
- the program modules 314 may, when loaded into the processing unit 302 and executed, transform the processing unit 302 and the overall computer 300 from a general-purpose computing system into a special-purpose computing system customized to allocate resources of a publisher web service to a subscriber web service according to the subscriber web service's SLA type.
- the processing unit 302 may be constructed from any number of transistors or other discrete circuit elements, which may individually or collectively assume any number of states. More specifically, the processing unit 302 may operate as a finite-state machine, in response to executable instructions contained within the program modules 314 . These computer-executable instructions may transform the processing unit 302 by specifying how the processing unit 302 transitions between states, thereby transforming the transistors or other discrete hardware elements constituting the processing unit 302 .
- Encoding the program modules 314 may also transform the physical structure of the computer-storage media.
- the specific transformation of physical structure may depend on various factors, in different implementations of this description. Examples of such factors may include, but are not limited to: the technology used to implement the computer-storage media, whether the computer-storage media are characterized as primary or secondary storage, and the like.
- the program modules 314 may transform the physical state of the semiconductor memory, when the software is encoded therein.
- the program modules 314 may transform the state of transistors, capacitors, or other discrete circuit elements constituting the semiconductor memory.
- the computer-storage media may be implemented using magnetic or optical technology.
- the program modules 314 may transform the physical state of magnetic or optical media, when the software is encoded therein. These transformations may include altering the magnetic characteristics of particular locations within given magnetic media. These transformations may also include altering the physical features or characteristics of particular locations within given optical media, to change the optical characteristics of those locations. Other transformations of physical media are possible without departing from the scope of the present description, with the foregoing examples provided only to facilitate this discussion.
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Information Transfer Between Computers (AREA)
Abstract
Description
- This application is a continuation of co-pending U.S. patent application Ser. No. 12/901,591, filed on Oct. 11, 2010, and titled “Allocation of Resources Between Web Services in a Composite Service,” the entire contents of which are hereby incorporated by reference herein.
- Conventional software applications have generally been installed and executed in a localized computing environment, such as a desktop or enterprise environment. The advancement of increasingly powerful computing devices and expanding data storage capacity in large scale networked data centers has moved consumer and business-oriented applications away from local computing environments to computing environments provided over the Internet or other types of networks, commonly referred to as “cloud-based” computing environments. These applications may be offered as hosted services in the cloud-based computing environment.
- As the Internet continues to grow, service providers may continue to offer more diverse hosted services. These hosted services may be offered at various levels, including end user services and various backend services. For example, a hosted service may offer one level of service to one hosted service and offer another level of service to another hosted service. The various levels of service may refer to different allocations of resources, such as processing resources, memory resources, networking resources, and/or the like. Combining these hosted services can yield a composite service. It is difficult, however, to integrate multiple levels of hosted services, especially when these hosted services are offered by different service providers.
- It is with respect to these considerations and others that the disclosure made herein is presented.
- Technologies are described herein for allocating resources of a publisher web service to a subscriber web service according to the subscriber web service's service level agreement (SLA) type. A composite service may include multiple web services, such as a first web service and a second web service. The second web service may utilize resources provided by the first web service. In order to utilize resources provided from the first web service, the second web service may subscribe to a level of service (e.g., the SLA type) from the first web service. In this case, the first web service may be referred to as the publisher web service, and the second web service may be referred to as the subscriber web service.
- Through the utilization of the technologies and concepts presented herein, the subscriber web service can send a request for information to the publisher web service. The request for information may include an identifier of the subscriber web service. The publisher web service may retrieve the SLA type associated with the identifier of the subscriber web service. The publisher web service may then allocate resources for satisfying the request for information based on the SLA type. In one example, the publisher web service may route the request for information to a server adapted to provide the information. The server can then provide the information directly to the subscriber web service in response to the request for information. In another example, the publisher web service may retrieve a uniform resource locator (URL) based on the SLA type. The URL may correspond to a server configured to provide the information. The subscriber web service can then access the URL in order to retrieve the information.
- Example technologies may provide for allocating resources between web services in a composite service. The technologies receive a request for information from a subscriber web service. The request for information may include a SLA type between a publisher web service and the subscriber web service and an identifier of the subscriber web service. The composite service may include the publisher web service and the subscriber web service. The technologies retrieve a resource allocation associated with the SLA type. The technologies allocate a set of resources from multiple resources of the publisher web service to the subscriber web service according to the resource allocation and the identifier. The set of resources may be configured to satisfy the request for information.
- It should be appreciated that the above-described subject matter may also be implemented as a computer-controlled apparatus, a computer process, a computing system, or as an article of manufacture such as a computer-readable storage medium. These and various other features will be apparent from a reading of the following Detailed Description and a review of the associated drawings.
- This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended that this Summary be used to limit the scope of the claimed subject matter. Furthermore, the claimed subject matter is not limited to implementations that solve any or all disadvantages noted in any part of this disclosure.
-
FIG. 1 is a block diagram illustrating a composite service adapted to allocate resources of a publisher web service to a subscriber web service according to the subscriber web service's SLA type, in accordance with some embodiment; -
FIG. 2 is a flow diagram illustrating a method for allocating resources of a publisher web service to a subscriber web service according to the subscriber web service's SLA type, in accordance with some embodiments; and -
FIG. 3 is a computer architecture diagram showing an illustrative computer hardware architecture for a computing system capable of implementing the embodiments presented herein. - The following detailed description is directed to technologies for allocating resources of a publisher web service to a subscriber web service according to the subscriber web service's SLA type. In accordance with some embodiments described herein, a composite service may include multiple web services. Each of these web services may be a publisher web service and/or a subscriber web service. A subscriber web service may refer to a web service that utilizes resources provided by a publisher web service. A subscriber web service may be associated with a SLA type corresponding to a particular publisher web service. A publisher web service may allocate resources for each corresponding subscriber web service depending on the subscriber web service's SLA type.
- While the subject matter described herein is presented in the general context of program modules that execute in conjunction with the execution of an operating system and application programs on a computer system, those skilled in the art will recognize that other implementations may be performed in combination with other types of program modules. Generally, program modules include routines, programs, components, data structures, and other types of structures that perform particular tasks or implement particular abstract data types. Moreover, those skilled in the art will appreciate that the subject matter described herein may be practiced with other computer system configurations, including hand-held devices, multiprocessor systems, microprocessor-based or programmable consumer electronics, minicomputers, mainframe computers, and the like.
- In the following detailed description, references are made to the accompanying drawings that form a part hereof, and which are shown by way of illustration, specific embodiments, or examples. Referring now to the drawings, in which like numerals represent like elements through the several figures, a computing system and methodology for allocating resources of a publisher web service to a subscriber web service according to the subscriber web service's SLA type will be described.
-
FIG. 1 illustrates acomposite service 100 adapted to allocate resources of a publisher web service to a subscriber web service according to the subscriber web service's SLA type, in accordance with some embodiments. Thecomposite service 100 may include afirst web service 102, asecond web service 104, and athird web service 106. The web services 102-106 may be coupled via acommunications network 108. An example of thecomposite service 100 is the monitoring service described in U.S. patent application Ser. No. 12/900,481, filed Oct. 8, 2010, entitled “Providing a Monitoring Service in a Cloud-Based Computing Environment,” Attorney Docket No. 330467.01, which is hereby incorporated by reference in its entirety. Some examples of the web services 102-106 include the various web services (e.g., controller application, monitor application, finder application, analyzer application, notifier application, etc.) also described in the above referenced and incorporated patent application entitled “Providing a Monitoring Service in a Cloud-Based Environment.” - The
first web service 102 may include aSLA module 109 and resource allocation table 110. The resource allocation table 110 may include afirst resource allocation 111A and asecond resource allocation 111B. Thesecond web service 104 may include arequest module 112A and aSLA type 114A. Thethird web service 106 may include arequest module 112B and aSLA type 114B. In the example illustrated inFIG. 1 , thefirst web service 102 may be referred to as a publisher web service, and thesecond web service 104 and thethird web service 106 may be referred to a subscriber web services. That is, thesecond web service 104 and thethird web service 106 may be configured to utilize resources provided by thefirst web service 102. The web services 102-106 may each be a publisher web service and/or a subscriber web service, according to various embodiments. - The
second web service 104 and thethird web service 106 may be associated withdifferent SLA types unique identifiers first web service 102. The SLA types 114A, 114B may also be associated with different fees paid by an operator of thesecond web service 104 and an operator of thethird web service 106 to an operator of thefirst web service 102. In some examples, the SLA types 114A, 114B may be shared with multiple publisher services. In other examples, the SLA types 114A, 114B may be associated with only thefirst web service 102, while other SLA types may be associated with other publisher web services. In the example illustrated inFIG. 1 , theSLA type 114A may correspond to a “platinum” level SLA type, and theSLA type 114B may correspond to a “silver” level SLA type. The platinum level may be associated with a higher allocation of resources than the silver level. It should be appreciated that the platinum level and silver level SLA types are merely illustrative, and other SLA types may be similarly utilized. - In an illustrative example, the
first web service 102 may be a search service. In this example, therequest modules SLA module 109. The request for information may include queries, the corresponding SLA types 114A, 114B, and theidentifiers second web service 104 and thethird web service 106. Upon receiving the request for information, theSLA module 109 may retrieveresource allocations SLA type 114A may correspond to theresource allocation 111A, and theSLA type 114B may correspond to theresource allocation 111B. - The
SLA module 109 may then allocate resources for performing the search service to thesecond web service 104 and thethird web service 106 according to the retrievedresource allocations identifiers SLA module 109 may allocate a first set of resources from multiple resources in thefirst web service 102 to thesecond web service 104. TheSLA module 109 may also allocate a second set of resources from the multiple resources in thefirst web service 102 to thethird web service 106. In some embodiments, the resource allocation table 110 may be stored in the memory of a computer operating thefirst web service 102. In other embodiments, the resource allocation table 110 may be stored in an external database accessible by a computer operating thefirst web service 102. - The resources may refer to one or more entities that a publisher web service is capable of allocating to multiple subscriber web services. Such resources may be allocated according to suitable business rules associated with the
various SLA types request module 112A sends a query to theSLA module 109, theSLA module 109 may allocate a dedicated server to thesecond web service 104 according to the platinum level. When therequest module 112B sends a query to theSLA module 109, theSLA module 109 may allocate a shared server to thethird web service 106 according to the silver level. The shared server may be shared by multiple web services. - The
SLA module 109 may allocate the dedicated server and the shared server by sending URLs corresponding to the dedicated server and the shared server to therequest modules second web service 104 and thethird web service 106 can then utilize the URLs in order to retrieve the search results. Alternatively, theSLA module 109 may route the query directly to the dedicated server and the shared server. The dedicated server and the shared server can then retrieve and provide the search results to thesecond web service 104 and thethird web service 106 without further action from thesecond web service 104 and thethird web service 106. - In a second embodiment, the resources may refer to a level of access. For example, when the
request module 112A sends a query to theSLA module 109, theSLA module 109 may assign access to a greater number of search providers to thesecond web service 104 according to the platinum level. When therequest module 112B sends a query to theSLA module 109, theSLA module 109 may assign a lesser number of search providers to thethird web service 106 according to the silver level. - In a third embodiment, the resources may refer to bandwidth or other suitable computer resources. For example, when the
request module 112A sends a query to theSLA module 109, theSLA module 109 may allocate additional computer resources to thesecond web service 104 according to the platinum level SLA. When therequest module 112B sends a query to theSLA module 109, theSLA module 109 may decrease available computer resources available to thethird web service 106 according to the silver level. - In a fourth embodiment, the resources may refer to service availability or uptime. For example, when the
request module 112A sends a query to theSLA module 109, theSLA module 109 may allocate a greater time of availability or uptime to thesecond web service 104 according to the platinum level. When therequest module 112B sends a query to theSLA module 109, theSLA module 109 may allocate a lesser time of availability or uptime to thethird web service 106 according to the silver level. - In a fifth embodiment, the resources may refer to a response time. For example, when the
request module 112A sends a query to theSLA module 109, theSLA module 109 may assign real-time or near real-time access of search results to thesecond web service 104 according to the platinum level. When therequest module 112B sends a query to theSLA module 109, theSLA module 109 may assign delayed access to thethird web service 106 according to the silver level. - As previously described, the
SLA module 109 may allocate resources according to suitable business rules associated with thevarious SLA types SLA module 109 routes a query to a particular shared server, theSLA module 109 may account for current server load. In this example, theSLA module 109 may route the query to a shared server having the lowest current load. In another example, where theSLA module 109 routes a query to a particular server, theSLA module 109 may account for current server availability. In this example, theSLA module 109 may route the query to a server having current availability to respond to the query. In yet another example, where theSLA module 109 routes a query to a particular server, theSLA module 109 may account for political requirements. In this example, theSLA module 109 may route the query to a server in China where business rules dictate that Chinese political requirements be met. - Referring now to
FIG. 2 , additional details regarding the operations of therequest modules SLA module 109 will be provided. In particular,FIG. 2 is a flow diagram illustrating a method for allocating resources of a publisher web service to a subscriber web service according to the subscriber web service's SLA type, in accordance with some embodiments. It should be appreciated that the logical operations described herein are implemented (1) as a sequence of computer implemented acts or program modules running on a computing system and/or (2) as interconnected machine logic circuits or circuit modules within the computing system. The implementation is a matter of choice dependent on the performance and other requirements of the computing system. Accordingly, the logical operations described herein are referred to variously as states operations, structural devices, acts, or modules. These operations, structural devices, acts, and modules may be implemented in software, in firmware, in special purpose digital logic, and any combination thereof. It should be appreciated that more or fewer operations may be performed than shown in the figures and described herein. These operations may also be performed in a different order than those described herein. - In
FIG. 2 a routine 200 begins atoperation 202, where theSLA module 109 receives a request for information from a subscriber web service, such as thesecond web service 104. That is, therequest module 112A may send the request for information to theSLA module 109. The request for information may include theSLA type 114A and theidentifier 116A. TheSLA type 114A may specify a level of service agreed between thesecond web service 104 and thefirst web service 102. For example, a higher fee paid by an operator of thesecond web service 104 to an operator of thefirst web service 102 may correspond to a higher level of service, while a lower fee paid by an operator of thesecond web service 104 to an operator of thefirst web service 102 may correspond to a lower level of service. Theidentifier 116A may identify and/or specify a location of thesecond web service 104. When theSLA module 109 receives the request for information from thesecond web service 104, the routine 200 may proceed tooperation 204. - At
operation 204, theSLA module 109 may retrieve a resource allocation associated with theSLA type 114A. In some embodiments, theSLA module 109 may retrieve theresource allocation 111A corresponding to theSLA type 114A from the resource allocation table 110. The resource allocation table 110 may include multiple SLA types, each of which corresponds to a particular resource allocation. That is, different SLA types may correspond to different resource allocations. When theSLA module 109 retrieves the resource allocation associated with theSLA type 114A, the routine 200 may proceed tooperation 206. - At
operation 206, theSLA module 109 allocates a set of resources of thefirst web service 102 to thesecond web service 104 according to the retrievedresource allocation 111A and theidentifier 116A. Thefirst web service 102 may include multiple resources. At least a portion of these resources may form the set of resources allocated to thefirst web service 102. TheSLA module 109 may determine the set of resources based on the retrievedresource allocation 111A. TheSLA module 109 may then allocate the set of resources to thesecond web service 104 as identified by theidentifier 116A. When theSLA module 109 allocates the set of resources of thefirst web service 102 to thesecond web service 104 according to the retrievedresource allocation 111A and theidentifier 116A, the routine 200 may repeat (e.g., periodically, continuously, or on demand as needed) or terminate. - Turning now to
FIG. 3 , an example computer architecture diagram showing acomputer 300 is illustrated. Thecomputer 300 may include acentral processing unit 302, asystem memory 304, and a system bus 306 that couples thememory 304 to the 302. Thecomputer 300 may further include amass storage device 312 for storing one ormore program modules 314 and thedatabase 316. Examples of theprogram modules 314 may include theSLA module 109 and therequest module 112A. Thedatabase 316 may store the resource allocation table 110. Themass storage device 312 may be connected to theprocessing unit 302 through a mass storage controller (not shown) connected to the bus 306. Themass storage device 312 and its associated computer-storage media may provide non-volatile storage for thecomputer 300. Although the description of computer-storage media contained herein refers to a mass storage device, such as a hard disk or CD-ROM drive, it should be appreciated by those skilled in the art that computer-storage media can be any available computer storage media that can be accessed by thecomputer 300. - By way of example, and not limitation, computer-storage media may include volatile and non-volatile, removable and non-removable media implemented in any method or technology for the non-transitory storage of information such as computer-storage instructions, data structures, program modules, or other data. For example, computer-storage media includes, but is not limited to, RAM, ROM, EPROM, EEPROM, flash memory or other solid state memory technology, CD-ROM, digital versatile disks (“DVD”), HD-DVD, BLU-RAY, or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by the
computer 300. - According to various embodiments, the
computer 300 may operate in a networked environment using logical connections to remote computers through a network such as thenetwork 108. Thecomputer 300 may connect to thenetwork 108 through a network interface unit 310 connected to the bus 306. It should be appreciated that the network interface unit 310 may also be utilized to connect to other types of networks and remote computer systems. Thecomputer 300 may also include an input/output controller 308 for receiving and processing input from a number of input devices (not shown), including a keyboard, a mouse, a microphone, and a game controller. Similarly, the input/output controller 308 may provide output to a display or other type of output device (not shown). - The bus 306 may enable the
processing unit 302 to read code and/or data to/from themass storage device 312 or other computer-storage media. The computer-storage media may represent apparatus in the form of storage elements that are implemented using any suitable technology, including but not limited to semiconductors, magnetic materials, optics, or the like. The computer-storage media may represent memory components, whether characterized as RAM, ROM, flash, or other types of technology. The computer-storage media may also represent secondary storage, whether implemented as hard drives or otherwise. Hard drive implementations may be characterized as solid state, or may include rotating media storing magnetically-encoded information. - The
program modules 314 may include software instructions that, when loaded into theprocessing unit 302 and executed, cause thecomputer 300 to allocate resources of a publisher web service to a subscriber web service according to the subscriber web service's SLA type. Theprogram modules 314 may also provide various tools or techniques by which thecomputer 300 may participate within the overall systems or operating environments using the components, flows, and data structures discussed throughout this description. For example, theprogram modules 314 may implement interfaces for allocating resources of a publisher web service to a subscriber web service according to the subscriber web service's SLA type. - In general, the
program modules 314 may, when loaded into theprocessing unit 302 and executed, transform theprocessing unit 302 and theoverall computer 300 from a general-purpose computing system into a special-purpose computing system customized to allocate resources of a publisher web service to a subscriber web service according to the subscriber web service's SLA type. Theprocessing unit 302 may be constructed from any number of transistors or other discrete circuit elements, which may individually or collectively assume any number of states. More specifically, theprocessing unit 302 may operate as a finite-state machine, in response to executable instructions contained within theprogram modules 314. These computer-executable instructions may transform theprocessing unit 302 by specifying how theprocessing unit 302 transitions between states, thereby transforming the transistors or other discrete hardware elements constituting theprocessing unit 302. - Encoding the
program modules 314 may also transform the physical structure of the computer-storage media. The specific transformation of physical structure may depend on various factors, in different implementations of this description. Examples of such factors may include, but are not limited to: the technology used to implement the computer-storage media, whether the computer-storage media are characterized as primary or secondary storage, and the like. For example, if the computer-storage media are implemented as semiconductor-based memory, theprogram modules 314 may transform the physical state of the semiconductor memory, when the software is encoded therein. For example, theprogram modules 314 may transform the state of transistors, capacitors, or other discrete circuit elements constituting the semiconductor memory. - As another example, the computer-storage media may be implemented using magnetic or optical technology. In such implementations, the
program modules 314 may transform the physical state of magnetic or optical media, when the software is encoded therein. These transformations may include altering the magnetic characteristics of particular locations within given magnetic media. These transformations may also include altering the physical features or characteristics of particular locations within given optical media, to change the optical characteristics of those locations. Other transformations of physical media are possible without departing from the scope of the present description, with the foregoing examples provided only to facilitate this discussion. - Based on the foregoing, it should be appreciated that technologies for allocating resources of a publisher web service to a subscriber web service according to the subscriber web service's SLA type are presented herein. Although the subject matter presented herein has been described in language specific to computer structural features, methodological acts, and computer readable media, it is to be understood that the invention defined in the appended claims is not necessarily limited to the specific features, acts, or media described herein. Rather, the specific features, acts and mediums are disclosed as example forms of implementing the claims.
- The subject matter described above is provided by way of illustration only and should not be construed as limiting. Various modifications and changes may be made to the subject matter described herein without following the example embodiments and applications illustrated and described, and without departing from the true spirit and scope of the present invention, which is set forth in the following claims.
Claims (1)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US14/491,059 US20150081914A1 (en) | 2010-10-11 | 2014-09-19 | Allocation of Resources Between Web Services in a Composite Service |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US12/901,591 US8843632B2 (en) | 2010-10-11 | 2010-10-11 | Allocation of resources between web services in a composite service |
US14/491,059 US20150081914A1 (en) | 2010-10-11 | 2014-09-19 | Allocation of Resources Between Web Services in a Composite Service |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/901,591 Continuation US8843632B2 (en) | 2010-10-11 | 2010-10-11 | Allocation of resources between web services in a composite service |
Publications (1)
Publication Number | Publication Date |
---|---|
US20150081914A1 true US20150081914A1 (en) | 2015-03-19 |
Family
ID=45925996
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/901,591 Active 2031-08-10 US8843632B2 (en) | 2010-10-11 | 2010-10-11 | Allocation of resources between web services in a composite service |
US14/491,059 Abandoned US20150081914A1 (en) | 2010-10-11 | 2014-09-19 | Allocation of Resources Between Web Services in a Composite Service |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/901,591 Active 2031-08-10 US8843632B2 (en) | 2010-10-11 | 2010-10-11 | Allocation of resources between web services in a composite service |
Country Status (1)
Country | Link |
---|---|
US (2) | US8843632B2 (en) |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9215154B2 (en) | 2010-10-08 | 2015-12-15 | Microsoft Technology Licensing, Llc | Providing a monitoring service in a cloud-based computing environment |
US9979631B2 (en) | 2010-10-18 | 2018-05-22 | Microsoft Technology Licensing, Llc | Dynamic rerouting of service requests between service endpoints for web services in a composite service |
US9979630B2 (en) | 2010-10-20 | 2018-05-22 | Microsoft Technology Licensing, Llc | Optimized consumption of third-party web services in a composite service |
Families Citing this family (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7509373B2 (en) | 2003-11-24 | 2009-03-24 | At&T Intellectual Property I, L.P. | Methods for providing communications services |
US8495218B1 (en) * | 2011-01-21 | 2013-07-23 | Google Inc. | Managing system resources |
US8813205B2 (en) * | 2012-02-06 | 2014-08-19 | International Business Machines Corporation | Consolidating disparate cloud service data and behavior based on trust relationships between cloud services |
US20150163157A1 (en) * | 2013-12-09 | 2015-06-11 | Alcatel-Lucent Usa Inc. | Allocation and migration of cloud resources in a distributed cloud system |
CN107295052B (en) | 2016-04-11 | 2020-06-09 | 阿里巴巴集团控股有限公司 | Service processing method and device |
US20180321981A1 (en) * | 2017-05-04 | 2018-11-08 | Huawei Technologies Co., Ltd. | System and method for self organizing data center |
US10476679B2 (en) * | 2017-11-14 | 2019-11-12 | INTEGRITY Security Services, Inc. | Systems, methods, and devices for multi-stage provisioning and multi-tenant operation for a security credential management system |
CN114666211B (en) * | 2020-12-23 | 2023-11-17 | 上海华为技术有限公司 | Communication method, model processing method and related equipment |
CN116436806B (en) * | 2023-06-12 | 2023-08-18 | 亚信科技(中国)有限公司 | Method and device for arranging computing network resources, electronic equipment and computer storage medium |
Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20050091374A1 (en) * | 2003-10-23 | 2005-04-28 | International Business Machines Corporation | Aspect oriented web service invocation |
Family Cites Families (62)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7162436B1 (en) | 1999-09-24 | 2007-01-09 | In-Development, Llc | System and method for pairing providers with consumers of online goods and services |
US6754699B2 (en) | 2000-07-19 | 2004-06-22 | Speedera Networks, Inc. | Content delivery and global traffic management network system |
US6950848B1 (en) | 2000-05-05 | 2005-09-27 | Yousefi Zadeh Homayoun | Database load balancing for multi-tier computer systems |
US7912978B2 (en) | 2000-07-19 | 2011-03-22 | Akamai Technologies, Inc. | Method for determining metrics of a content delivery and global traffic management network |
US6816907B1 (en) | 2000-08-24 | 2004-11-09 | International Business Machines Corporation | System and method for providing differentiated services on the web |
US20030061365A1 (en) | 2001-03-14 | 2003-03-27 | Microsoft Corporation | Service-to-service communication for network services |
US7302634B2 (en) | 2001-03-14 | 2007-11-27 | Microsoft Corporation | Schema-based services for identity-based data access |
US7269157B2 (en) | 2001-04-10 | 2007-09-11 | Internap Network Services Corporation | System and method to assure network service levels with intelligent routing |
US20020194324A1 (en) | 2001-04-26 | 2002-12-19 | Aloke Guha | System for global and local data resource management for service guarantees |
US20030149735A1 (en) | 2001-06-22 | 2003-08-07 | Sun Microsystems, Inc. | Network and method for coordinating high availability system services |
JP3879471B2 (en) | 2001-10-10 | 2007-02-14 | 株式会社日立製作所 | Computer resource allocation method |
US7062472B2 (en) | 2001-12-14 | 2006-06-13 | International Business Machines Corporation | Electronic contracts with primary and sponsored roles |
US20040064528A1 (en) | 2002-09-30 | 2004-04-01 | Microsoft Corporation | Safe interoperability among web services |
US7783499B2 (en) | 2003-03-03 | 2010-08-24 | International Business Machines Corporation | Framework for dynamic composition of web services |
GB0305959D0 (en) | 2003-03-15 | 2003-04-23 | Ibm | Client web service access |
WO2004107216A2 (en) | 2003-05-23 | 2004-12-09 | Computer Associates Think, Inc. | A publish/subscribe mechanism for web services |
US7194642B2 (en) | 2003-08-04 | 2007-03-20 | Intel Corporation | Technique to coordinate servicing of multiple network interfaces |
US20050038867A1 (en) | 2003-08-14 | 2005-02-17 | International Business Machines Corporation | Method, system and program product for integrating web services on a client |
US8949311B2 (en) | 2003-08-29 | 2015-02-03 | International Business Machines Corporation | Dynamic, non-intrusive personalization of web services |
US20050172027A1 (en) | 2004-02-02 | 2005-08-04 | Castellanos Maria G. | Management of service level agreements for composite Web services |
US7552170B2 (en) | 2004-02-26 | 2009-06-23 | Research In Motion Limited | Apparatus and method for aggregating web services |
US20050251823A1 (en) | 2004-05-05 | 2005-11-10 | Nokia Corporation | Coordinated cross media service |
US7310684B2 (en) | 2004-05-21 | 2007-12-18 | Bea Systems, Inc. | Message processing in a service oriented architecture |
US8458467B2 (en) | 2005-06-21 | 2013-06-04 | Cisco Technology, Inc. | Method and apparatus for adaptive application message payload content transformation in a network infrastructure element |
US7543023B2 (en) | 2005-03-15 | 2009-06-02 | Microsoft Corporation | Service support framework for peer to peer applications |
US7743001B1 (en) | 2005-06-21 | 2010-06-22 | Amazon Technologies, Inc. | Method and system for dynamic pricing of web services utilization |
US7383247B2 (en) | 2005-08-29 | 2008-06-03 | International Business Machines Corporation | Query routing of federated information systems for fast response time, load balance, availability, and reliability |
US8316104B2 (en) | 2005-11-15 | 2012-11-20 | California Institute Of Technology | Method and apparatus for collaborative system |
US8429673B2 (en) | 2006-04-26 | 2013-04-23 | Sap Ag | Systems and methods of accessing information across distributed computing components |
JP2010502116A (en) | 2006-08-18 | 2010-01-21 | ソニー株式会社 | System and method for selective media content access by recommendation engine |
US20090182955A1 (en) | 2006-09-08 | 2009-07-16 | Rao Cherukuri | Application configuration across client devices of a local system |
US8014308B2 (en) | 2006-09-28 | 2011-09-06 | Microsoft Corporation | Hardware architecture for cloud services |
US8595356B2 (en) | 2006-09-28 | 2013-11-26 | Microsoft Corporation | Serialization of run-time state |
US20080104393A1 (en) | 2006-09-28 | 2008-05-01 | Microsoft Corporation | Cloud-based access control list |
US20080080396A1 (en) | 2006-09-28 | 2008-04-03 | Microsoft Corporation | Marketplace for cloud services resources |
CN101163120B (en) | 2006-10-13 | 2011-12-21 | 华为技术有限公司 | Method and system of cooperating services provided by different service providers |
US7984158B2 (en) | 2007-03-20 | 2011-07-19 | Microsoft Corporation | Web service for coordinating actions of clients |
US8453159B2 (en) | 2007-05-31 | 2013-05-28 | Informatica Corporation | Workspace system and method for monitoring information events |
US8046429B2 (en) | 2007-06-25 | 2011-10-25 | Nokia Corporation | Service mobility for composed components |
CA2691659A1 (en) | 2007-06-28 | 2009-01-08 | Neustar, Inc. | Monitoring web service transactions |
US8122444B2 (en) | 2007-08-02 | 2012-02-21 | Accenture Global Services Limited | Legacy application decommissioning framework |
US20090089078A1 (en) | 2007-09-28 | 2009-04-02 | Great-Circle Technologies, Inc. | Bundling of automated work flow |
US20090150565A1 (en) | 2007-12-05 | 2009-06-11 | Alcatel Lucent | SOA infrastructure for application sensitive routing of web services |
US7986707B2 (en) | 2008-02-11 | 2011-07-26 | International Business Machines Corporation | Method and system for rules based workflow of media services |
US8620889B2 (en) | 2008-03-27 | 2013-12-31 | Microsoft Corporation | Managing data transfer between endpoints in a distributed computing environment |
US20100030866A1 (en) | 2008-07-23 | 2010-02-04 | Ameya Computing, Inc. | Method and system for real-time cloud computing |
US20100076856A1 (en) | 2008-09-25 | 2010-03-25 | Microsoft Corporation | Real-Time Auction of Cloud Computing Resources |
US8271974B2 (en) | 2008-10-08 | 2012-09-18 | Kaavo Inc. | Cloud computing lifecycle management for N-tier applications |
US8782233B2 (en) | 2008-11-26 | 2014-07-15 | Red Hat, Inc. | Embedding a cloud-based resource request in a specification language wrapper |
US9870541B2 (en) * | 2008-11-26 | 2018-01-16 | Red Hat, Inc. | Service level backup using re-cloud network |
US20100153482A1 (en) | 2008-12-10 | 2010-06-17 | Full Armor Corporation | Cloud-Based Automation of Resources |
US8341427B2 (en) | 2009-02-16 | 2012-12-25 | Microsoft Corporation | Trusted cloud computing and services framework |
CA2763148C (en) | 2009-05-20 | 2016-11-22 | Redcliff Investments, L.L.C. | Secure workflow and data management facility |
WO2011091056A1 (en) * | 2010-01-19 | 2011-07-28 | Servicemesh, Inc. | System and method for a cloud computing abstraction layer |
US8504400B2 (en) | 2010-03-24 | 2013-08-06 | International Business Machines Corporation | Dynamically optimized distributed cloud computing-based business process management (BPM) system |
US20110276490A1 (en) * | 2010-05-07 | 2011-11-10 | Microsoft Corporation | Security service level agreements with publicly verifiable proofs of compliance |
US8364819B2 (en) * | 2010-05-28 | 2013-01-29 | Red Hat, Inc. | Systems and methods for cross-vendor mapping service in cloud networks |
US8776076B2 (en) * | 2010-07-20 | 2014-07-08 | Nec Laboratories America, Inc. | Highly scalable cost based SLA-aware scheduling for cloud services |
US20120066487A1 (en) | 2010-09-09 | 2012-03-15 | Novell, Inc. | System and method for providing load balancer visibility in an intelligent workload management system |
US9262228B2 (en) | 2010-09-23 | 2016-02-16 | Microsoft Technology Licensing, Llc | Distributed workflow in loosely coupled computing |
US8380845B2 (en) | 2010-10-08 | 2013-02-19 | Microsoft Corporation | Providing a monitoring service in a cloud-based computing environment |
US20120124193A1 (en) | 2010-11-12 | 2012-05-17 | International Business Machines Corporation | Identification of Critical Web Services and their Dynamic Optimal Relocation |
-
2010
- 2010-10-11 US US12/901,591 patent/US8843632B2/en active Active
-
2014
- 2014-09-19 US US14/491,059 patent/US20150081914A1/en not_active Abandoned
Patent Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20050091374A1 (en) * | 2003-10-23 | 2005-04-28 | International Business Machines Corporation | Aspect oriented web service invocation |
Cited By (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9215154B2 (en) | 2010-10-08 | 2015-12-15 | Microsoft Technology Licensing, Llc | Providing a monitoring service in a cloud-based computing environment |
US9660884B2 (en) | 2010-10-08 | 2017-05-23 | Microsoft Technology Licensing, Llc | Providing a monitoring service in a cloud-based computing environment |
US10038619B2 (en) | 2010-10-08 | 2018-07-31 | Microsoft Technology Licensing, Llc | Providing a monitoring service in a cloud-based computing environment |
US9979631B2 (en) | 2010-10-18 | 2018-05-22 | Microsoft Technology Licensing, Llc | Dynamic rerouting of service requests between service endpoints for web services in a composite service |
US9979630B2 (en) | 2010-10-20 | 2018-05-22 | Microsoft Technology Licensing, Llc | Optimized consumption of third-party web services in a composite service |
Also Published As
Publication number | Publication date |
---|---|
US8843632B2 (en) | 2014-09-23 |
US20120089734A1 (en) | 2012-04-12 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8843632B2 (en) | Allocation of resources between web services in a composite service | |
US11836533B2 (en) | Automated reconfiguration of real time data stream processing | |
US9979631B2 (en) | Dynamic rerouting of service requests between service endpoints for web services in a composite service | |
US10127086B2 (en) | Dynamic management of data stream processing | |
US10447772B2 (en) | Managed function execution for processing data streams in real time | |
US10129118B1 (en) | Real time anomaly detection for data streams | |
US10367719B2 (en) | Optimized consumption of third-party web services in a composite service | |
JP2017538200A (en) | Service addressing in a distributed environment | |
US10303678B2 (en) | Application resiliency management using a database driver | |
US20160352821A1 (en) | Method and system for allocating resources for virtual hosts | |
US11178197B2 (en) | Idempotent processing of data streams | |
CN110781159B (en) | Ceph directory file information reading method and device, server and storage medium | |
US10545677B2 (en) | Volatile account identification and isolation and resource management in distributed data storage systems | |
US10528400B2 (en) | Detecting deadlock in a cluster environment using big data analytics | |
US10171378B2 (en) | System and method for allocating and reserving supervisors in a real-time distributed processing platform | |
CN110753136A (en) | Domain name resolution method, device, equipment and storage medium | |
US11722451B2 (en) | Distributing event messages from a first service to additional services using a message store | |
US20230409575A1 (en) | Database query processing with database clients | |
US9805113B2 (en) | Intelligent indexing | |
US9501229B1 (en) | Multi-tiered coarray programming |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: MICROSOFT CORPORATION, WASHINGTON Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MERCURI, MARC;REEL/FRAME:033779/0803 Effective date: 20101006 |
|
AS | Assignment |
Owner name: MICROSOFT TECHNOLOGY LICENSING, LLC, WASHINGTON Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MICROSOFT CORPORATION;REEL/FRAME:034747/0417 Effective date: 20141014 Owner name: MICROSOFT TECHNOLOGY LICENSING, LLC, WASHINGTON Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MICROSOFT CORPORATION;REEL/FRAME:039025/0454 Effective date: 20141014 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |