Composite service refactoring

• US 8,930,935 B2
• Filed: 12/28/2009
• Issued: 01/06/2015
• Est. Priority Date: 12/28/2009
• Status: Active Grant

• Current Assignee: Verizon Patent and Licensing Incorporated (Verizon Communications Inc.)
• Original Assignee: Verizon Patent and Licensing Incorporated (Verizon Communications Inc.)
• Inventors: Schultz, Paul T., Dwight, Timothy M., Hahn, Mark J., McKee, Martin W., Sartini, Robert A.
• Primary Examiner(s): Wong, Don
• Assistant Examiner(s): Aguilera, Todd
• Application Number:
  US12/647,855
• Publication Number:
  US 20110161911A1
• Time in Patent Office: 1,835 Days
• Field of Search: None
• US Class Current: 717/171
• CPC Class Codes: G06F 8/36 Software reuse
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management

Abstract

A network device may include a memory to store instructions. The network device may further include a processor to execute the instructions to obtain information relating to a loosely-coupled composite service, where the loosely-coupled composite service includes a group of services. The processor may further execute the instructions to analyze the obtained information to determine one or more design recommendations, and re-factor the loosely-coupled composite service as a target composite platform based on at least one of the one or more design recommendations.

Claims

1. A network device comprising:

one or more processors to;

obtain information relating to a loosely-coupled composite service,

the loosely-coupled composite service including a plurality of services, and

the plurality of services including a first service, a second service, and a third service

determine one or more design recommendations by analyzing the information relating to the loosely-coupled composite service, and

re-factor the loosely-coupled composite service to form a target composite service based on at least one of the one or more design recommendations,

the target composite service comprising the first service and the third service tightly coupled within one or more servers while the second service remains loosely coupled,

the second service remaining implemented outside of the one or more servers and the one or more servers accessing the second service via a network due to the second service being loosely coupled to the one or more servers, and

the one or more processors are to re-factor the loosely-coupled composite service based on the at least one of the one or more design recommendations by;

converting the plurality of services into Open Services Gateway initiative service components,

converting interfaces of the plurality of services into inter-process communications interfaces,

creating an Open Services Gateway initiative Manifest for description, maintenance, and upgrade of the Open Services Gateway initiative service components, and

producing the target composite service as an Open Services Gateway initiative bundle.

2. The network device of claim 1, where, when obtaining the information relating to the loosely-coupled composite service, the one or more processors are to at least one of:

obtain descriptive information that describes the plurality of services by using at least one of Universal Description Discovery and Integration (UDDI), Web Services Inspection Language (WSIL), or Web Services Description Language (WSDL),

obtain source code for at least one service of the plurality of services,

obtain information relating to messages transmitted to or from the plurality of services,

obtain latency information relating to the plurality of services,

obtain performance characteristics of the plurality of services,

obtain information relating to the one or more servers, or

obtain geographic locations of devices used to implement the loosely-coupled composite service.

3. The network device of claim 1, where the one or more processors are further to:

provide information regarding the one or more design recommendations, and

receive information indicating a selection of the at least one of the one or more design recommendations.

4. The network device of claim 1, where each of the one or more design recommendations improves at least one of performance, reliability, or scalability of the plurality of services.

5. The network device of claim 1, where, when determining the one or more design recommendations by analyzing the information relating to the loosely-coupled composite service, the one or more processors are to perform at least one of:

a traffic analysis of traffic transmitted to or from the plurality of services,

a performance analysis of source code of at least one service of the plurality of services to identify one or more sections of the source code to be rewritten in a different programming language,

a network latency analysis of latency information relating to the plurality of services, or

a topology analysis of information identifying geographic locations of devices used to implement the plurality of services,

the information relating to the loosely-coupled composite service including one or more of the traffic, the source code, the latency information, or the information identifying the geographic locations of the devices.

6. A method comprising:

receiving, by a refactoring platform, information relating to a loosely-coupled composite service,

the loosely-coupled composite service including a plurality of services, and

the plurality of services including a first service, a second service, and a third service;

determining, by the refactoring platform, one or more design recommendations by analyzing the information relating to the loosely-coupled composite service;

receiving, by the refactoring platform and from a user, an input that indicates a selection of at least one design recommendation of the one or more design recommendations; and

refactoring, by the refactoring platform and based on the input that indicates the selection of the at least one design recommendation, the loosely-coupled composite service to form a target composite service,

the target composite service comprising the first service and the third service tightly coupled within one or more servers while the second service remains loosely coupled,

the second service remaining implemented outside of the one or more servers and the one or more servers accessing the second service via a network due to the second service being loosely coupled to the one or more servers, and

refactoring the loosely-coupled composite service based on the input that indicates the selection of the at least one design recommendation by;

converting the plurality of services into Open Services Gateway initiative service components,

converting interfaces of the plurality of services into inter-process communications interfaces,

creating an Open Services Gateway initiative Manifest for description, maintenance, and upgrade of the Open Services Gateway initiative service components, and

producing the target composite service as an Open Services Gateway initiative bundle.

7. The method of claim 6,

where the information relating to the loosely-coupled composite service includes descriptive information for the plurality of services, and

where the descriptive information includes two or more of:

information identifying one or more entities that control the plurality of services,

information identifying capabilities of the plurality of services,

information indicating how the plurality of services work, or

information for constructing one or more classes for the plurality of services.

8. The method of claim 6, where the information relating to the loosely-coupled composite service includes source code for at least one of the first service or the second service.

9. The method of claim 8,

where the source code is in a first programming language, and

where the one or more design recommendations include:

a design recommendation to convert all or a portion of the source code from the first programming language to a second programming language,

where the first programming language is different from the second programming language.

10. The method of claim 6,

where receiving the information relating to the loosely-coupled composite service includes:

receiving messages transmitted between the plurality of services and the one or more servers, and

determining, based on the messages, interface information regarding at least one interface between the plurality of services and the one or more servers, and

where the information relating to the loosely-coupled composite service includes the interface information.

11. The method of claim 6,

where the information relating to the loosely-coupled composite service includes information regarding the one or more servers.

12. The method of claim 6,

where the information relating to the loosely-coupled composite service includes at least one of:

information regarding network latency relating to accessing the plurality of services of the loosely-coupled composite service, or

information regarding geographic locations of devices used in implementing the loosely-coupled composite service.

13. The method of claim 6, where refactoring the loosely-coupled composite service includes:

converting a messaging interface of the first service or the second service into an inter-process communications interface.

14. A non-transitory computer-readable medium storing instructions, the instructions comprising:

one or more instructions that, when executed by one or more processors, cause the one or more processors to;

receive information relating to a loosely-coupled composite service,

the loosely-coupled composite service including a plurality of services, and

the plurality of services including a first service, a second service, and a third service;

determine one or more design recommendations by analyzing the information relating to the loosely-coupled composite service, and

re-factor the loosely-coupled composite service to form a target composite service based on at least one of the one or more design recommendations,

the target composite service comprising the first service and the third service tightly coupled within one or more servers while the second service remains loosely coupled,

the second service remaining implemented outside of the one or more servers and the one or more servers accessing the second service via a network due to the second service being loosely coupled to the one or more servers, and

the one or more instructions that, when executed by the one or more processors, cause the one or more processors to re-factor the loosely-coupled composite service based on the at least one of the one or more design recommendations by;

converting the plurality of services into Open Services Gateway initiative service components,

converting interfaces of the plurality of services into inter-process communications interfaces,

creating an Open Services Gateway initiative Manifest for description, maintenance, and upgrade of the Open Services Gateway initiative service components, and

producing the target composite service as an Open Services Gateway initiative bundle.

15. The non-transitory computer-readable medium of claim 14, the instructions further comprising:

one or more instructions that, when executed by the one or more processors, cause the one or more processors to;

provide information regarding the one or more design recommendations; and

receive information regarding a selection of the at least one of the one or more design recommendations.

16. The non-transitory computer-readable medium of claim 14, where each of the one or more design recommendations improves at least one of a performance, a reliability, or a scalability of the plurality of services.

17. The non-transitory computer-readable medium of claim 14, where the one or more instructions to re-factor the loosely-coupled composite service include:

one or more instructions that, when executed by the one or more processors, cause the one or more processors to;

produce the target composite service for the first service and the second service to run as a bundle within a virtual machine.