Transition architecture from monolithic systems to microservice-based systems

• US 10,637,952 B1
• Filed: 12/19/2018
• Issued: 04/28/2020
• Est. Priority Date: 12/19/2018
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP SE
• Inventors: Koenig, Steffen, Jahr, Andreas
• Primary Examiner(s): Chan, Wing F
• Assistant Examiner(s): Ng, Billy H
• Application Number:
  US16/224,888
• Time in Patent Office: 496 Days
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/1031 Controlling of the operation of servers by a load balancer, e.g. adding or removing servers that serve requests
• CPC Class Codes: H04L 67/1034 Reaction to server failures by a load balancer
• CPC Class Codes: H04L 67/51 Discovery or management thereof, e.g. service location protocol [SLP] or web services
• CPC Class Codes: H04L 67/562 Brokering proxy services
• CPC Class Codes: H04L 67/565 Conversion or adaptation of application format or content adding application control or application functional data H04L67/561

Abstract

Methods, systems, and computer-readable storage media for providing a transition service broker, the transition service broker including a service registry proxy, and a service registry, the service proxy registry registering service proxies, each service proxy enabling interaction between at least one core component of a legacy core, and one or more external services, the service registry registering services available for consumption by core components of the legacy core, each external service of the external services including a service facade that maps between a legacy architecture, and the service, during a transition period between the legacy architecture, and the microservices-based architecture: establishing a connection between the at least one core component, and an external service through a service proxy, and receiving input from the external service through the connection, the input being processed by the at least one core component during execution of the software product in the legacy architecture.

Claims

1. A computer-implemented method for re-platforming a software product from a legacy architecture to a microservices-based architecture, the method being executed by one or more processors and comprising:

providing, within a legacy system of the legacy architecture, a transition service broker, the transition service broker comprising a service proxy registry, and a service registry, the service proxy registry registering service proxies, each service proxy enabling interaction between at least one core component of a legacy core, and one or more external services, the service registry registering services available for consumption by core components of the legacy core, each external service of the one or more external services comprising a service facade that maps between the legacy architecture, and the service;

during a transition period between the legacy architecture, and the microservices-based architecture;

establishing a connection between the at least one core component, and an external service through a service proxy, and

receiving input from the external service through the connection, the input being processed by the at least one core component during execution of the software product in the legacy architecture.

2. The method of claim 1, wherein the transition service broker comprises a package isolation manager that assigns an existing package to a service as an assigned package, and changes a visibility of the assigned package to restrict access to the assigned package to an interface of the service.

3. The method of claim 1, wherein the service broker comprises a state recovery manager that is configured to delete a service instance that is existing and includes a state, and is further configured to restart the service instance, and determine whether the state was fully recovered after restart.

4. The method of claim 1, wherein the transition service broker comprises a facade for communication between core components of the legacy core, and the service proxy registry.

5. The method of claim 1, wherein the service proxy registry provides a lookup mechanism for service proxies that provide a protocol-independent, callable interface to external services.

6. The method of claim 1, wherein the transition service broker registers, monitors and integrates the external services for consumption by the legacy core during the transition, and registers one or more components as services to be consumed by one or more other core components during the transition.

7. The method of claim 1, wherein the service registry periodically performs status checks on registered services, and stores status of the registered services.

8. A non-transitory computer-readable storage medium coupled to one or more processors and having instructions stored thereon which, when executed by the one or more processors, cause the one or more processors to perform operations for replatforming a software product from a legacy architecture to a microservices-based architecture, the operations comprising:

providing, within a legacy system of the legacy architecture, a transition service broker, the transition service broker comprising a service proxy registry, and a service registry, the service proxy registry registering service proxies, each service proxy enabling interaction between at least one core component of a legacy core, and one or more external services, the service registry registering services available for consumption by core components of the legacy core, each external service of the one or more external services comprising a service facade that maps between the legacy architecture, and the service;

during a transition period between the legacy architecture, and the microservices-based architecture;

establishing a connection between the at least one core component, and an external service through a service proxy, and

receiving input from the external service through the connection, the input being processed by the at least one core component during execution of the software product in the legacy architecture.

9. The computer-readable storage medium of claim 8, wherein the transition service broker comprises a package isolation manager that assigns an existing package to a service as an assigned package, and changes a visibility of the assigned package to restrict access to the assigned package to an interface of the service.

10. The computer-readable storage medium of claim 8, wherein the service broker comprises a state recovery manager that is configured to delete a service instance that is existing and includes a state, and is further configured to restart the service instance, and determine whether the state was fully recovered after restart.

11. The computer-readable storage medium of claim 8, wherein the transition service broker comprises a facade for communication between core components of the legacy core, and the service proxy registry.

12. The computer-readable storage medium of claim 8, wherein the service proxy registry provides a lookup mechanism for service proxies that provide a protocol-independent, callable interface to external services.

13. The computer-readable storage medium of claim 8, wherein the transition service broker registers, monitors and integrates the external services for consumption by the legacy core during the transition, and registers one or more components as services to be consumed by one or more other core components during the transition.

14. The computer-readable storage medium of claim 8, wherein the service registry periodically performs status checks on registered services, and stores status of the registered services.

15. A system, comprising:

a computing device; and

a computer-readable storage device coupled to the computing device and having instructions stored thereon which, when executed by the computing device, cause the computing device to perform operations for re-platforming a software product from a legacy architecture to a microservices-based architecture, the operations comprising;

providing, within a legacy system of the legacy architecture, a transition service broker, the transition service broker comprising a service proxy registry, and a service registry, the service proxy registry registering service proxies, each service proxy enabling interaction between at least one core component of a legacy core, and one or more external services, the service registry registering services available for consumption by core components of the legacy core, each external service of the one or more external services comprising a service facade that maps between the legacy architecture, and the service;

during a transition period between the legacy architecture, and the microservices-based architecture;

establishing a connection between the at least one core component, and an external service through a service proxy, and

receiving input from the external service through the connection, the input being processed by the at least one core component during execution of the software product in the legacy architecture.

16. The system of claim 15, wherein the transition service broker comprises a package isolation manager that assigns an existing package to a service as an assigned package, and changes a visibility of the assigned package to restrict access to the assigned package to an interface of the service.

17. The system of claim 15, wherein the service broker comprises a state recovery manager that is configured to delete a service instance that is existing and includes a state, and is further configured to restart the service instance, and determine whether the state was fully recovered after restart.

18. The system of claim 15, wherein the transition service broker comprises a facade for communication between core components of the legacy core, and the service proxy registry.

19. The system of claim 15, wherein the service proxy registry provides a lookup mechanism for service proxies that provide a protocol-independent, callable interface to external services.

20. The system of claim 15, wherein the transition service broker registers, monitors and integrates the external services for consumption by the legacy core during the transition, and registers one or more components as services to be consumed by one or more other core components during the transition.