COMPOSITE SERVICE REFACTORING

• US 20110161911A1
• Filed: 12/28/2009
• Published: 06/30/2011
• 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: DWIGHT, Timothy M., MCKEE, Martin W., HAHN, Mark J., SCHULTZ, Paul T., SARTINI, Robert A.
• Granted Patent: US 8,930,935 B2
• Time in Patent Office: Days
• US Class Current: 717/101
• 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 method comprising:

receiving, at a refactoring platform, information relating to a loosely-coupled composite service, the loosely-coupled composite service including a plurality of services;

analyzing, by the refactoring platform, the received information to determine one or more design recommendations;

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

refactoring, by the refactoring platform and based on the received input, the loosely-coupled composite service as a target composite service, the target composite service tightly coupling at least one of the plurality of services.

2. The method of claim 1, where the receiving information relating to the loosely-coupled composite service includes:

receiving descriptive information for the plurality of services, and

where the analyzing includes;

analyzing the descriptive information to make the one or more design recommendations.

3. The method of claim 1, where the receiving information relating to the loosely-coupled composite service includes:

receiving source code for at least one service of the plurality of services, and where the analyzing includes;

analyzing the source code to make one or more design recommendations.

4. The method of claim 3, where the source code is in a first programming language, and

where the one or more recommendations include:

a recommendation to convert all or a portion of the source code to a second, different programming language.

5. The method of claim 1, where the loosely-coupled composite service is implemented on one or more application servers,

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

receiving information regarding an interface between one service of the plurality of services and one application service of the one or more application servers, and

where the analyzing includes;

analyzing the interface information to make the one or more design recommendations.

6. The method of claim 1, where the loosely-coupled composite service is implemented on one or more application servers,

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

receiving information regarding the one or more application servers, and where the analyzing includes;

analyzing the information regarding the one or more application servers to make the one or more design recommendations.

7. The method of claim 1, where the receiving information relating to the loosely-coupled composite service includes at least one of:

receiving information regarding network latency relating to providing the loosely-coupled composite service, or

receiving information regarding network topology of devices used in providing the loosely-coupled composite service, and

where the analyzing includes;

analyzing the at least one of the received information regarding network latency or the received information regarding network topology to make the one or more recommendations.

8. The method of claim 1, where the refactoring includes:

converting a messaging interface of one service, of the plurality of services, into an inter-process communications interface.

9. The method of claim 1, where the refactoring includes:

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

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

creating an OSGi Manifest for description, maintenance, and upgrade of the OSGi service components, and

producing the target composite service as an OSGi bundle.

10. A network device comprising:

a memory to store instructions; and

a processor to execute the instructions to;

obtain information relating to a loosely-coupled composite service, the loosely-coupled composite service including a plurality of services,

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.

11. The network device of claim 10, where when obtaining information relating to the loosely-coupled composite service, the processor is to at least one of:

obtain descriptive information for the plurality of services 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 an application server that implements the loosely-coupled composite service, or

obtain network topology information relating to the loosely-coupled composite service.

12. The network device of claim 10, where the processor is further to:

provide the one or more design recommendations to a user, and

receive selection, from the user, of the at least one design recommendation of the one or more design recommendations.

13. The network device of claim 10, where each design recommendation, of the plurality of design recommendations, includes a recommendation that, if used in refactoring the loosely-coupled composite service, improves at least one of performance, reliability, or scalability of the loosely-coupled composite service.

14. The network device of claim 10, where, when refactoring the loosely-coupled composite service, the processor is to:

convert the plurality of services into Open Services Gateway initiative (OSGi) service components,

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

create an OSGi Manifest for description, maintenance, and upgrade of the OSGi service components, and

produce the target composite service as an OSGi bundle.

15. The network device of claim 10, where the processor executes the instructions to implement at least one of:

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

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

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

a topology analysis component to analyze information identifying geographic locations of devices used to implement the plurality of services.

16. A computer-readable medium that includes instructions for execution by one or more processors, the computer-readable medium comprising:

one or more instructions to receive information relating to a loosely-coupled composite service, the loosely-coupled composite service including a plurality of services, the received information including at least one of;

descriptive information for the plurality of services,

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

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

latency information relating to the plurality of services,

performance characteristics of the plurality of services,

information relating to an application server that implements the loosely-coupled composite service, or

network topology information relating to the loosely-coupled composite service;

one or more instructions to analyze the received information to determine one or more design recommendations, and

one or more instructions to re-factor the loosely-coupled composite service as a target composite platform based on at least one of the one or more design recommendations, the target composite service tightly coupling at least one of the plurality of services.

17. The computer-readable medium of claim 16, further comprising:

one or more instructions to provide the one or more design recommendations to a user; and

one or more instructions to receive selection, from the user, of the at least one design recommendation of the one or more design recommendations.

18. The computer-readable medium of claim 16, where each design recommendation, of the plurality of design recommendations, includes a recommendation that, if used in refactoring the loosely-coupled composite service, improves at least one of performance, reliability, or scalability of the loosely-coupled composite service.

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

one or more instructions to cause the plurality of services to run on a Java Virtual Machine.

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

one or more instructions to convert the plurality of services into Open Services Gateway initiative (OSGi) service components,

one or more instructions to convert interfaces of the plurality of services into inter-process communications interfaces,

one or more instructions to create an OSGi Manifest for description, maintenance, and upgrade of the OSGi service components, and

one or more instructions to produce the target composite service as an OSGi bundle.