INFINITE MICRO-SERVICES ARCHITECTURE

• US 20180309802A1
• Filed: 04/25/2017
• Published: 10/25/2018
• Est. Priority Date: 04/25/2017
• Status: Active Grant

• Current Assignee: GE Digital Holdings LLC (GE Aerospace)
• Original Assignee: General Electric Company
• Inventors: Sahu, Akshay
• Granted Patent: US 10,511,651 B2
• Time in Patent Office: Days
• CPC Class Codes: H04L 61/106 across networks, e.g. mapping telephone numbers to data network addresses
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]

Abstract

A plurality of micro-services is automatically registered with a central data storage device. During registration, a mapping is determined between intermediate identifiers that identify selected micro-services and physical addresses of one or more servers that execute the selected micro-services. At least one of the physical addresses are dynamically updated based upon operational changes to the one or more servers or based upon a registration of an additional server.

Claims

1. A method, comprising:

automatically registering a plurality of micro-services with a central data storage device, the registering including determining a mapping between intermediate identifiers that identify selected micro-services and physical addresses of one or more servers that execute the selected micro-services;

dynamically updating at least one of the physical addresses based upon operational changes to the one or more servers or based upon a registration of an additional server.

2. The method of claim 1, wherein the plurality of micro-services include a first micro-service and a second micro-service, and further comprising:

executing the first micro-service, the first micro-service programmatically calling the second micro-service, the first micro-service accessing the second micro-service via a first intermediate identifier that identifies the second micro-service;

accessing the mapping and obtaining a physical address of a server that executes the second micro-service using the first intermediate identifier;

executing the second micro-service by utilizing the physical address obtained from the mapping.

3. The method of claim 1, wherein the physical addresses are URLs.

4. The method of claim 1, wherein the registering further includes mapping each of the intermediate identifiers to one or more of:

a HTTP method, an input consumption by a selected micro-service, an output production by a selected micro-service, and a version number.

5. The method of claim 1, wherein the mapping is between a first selected intermediate identifier and a first plurality of physical addresses.

6. The method of claim 5, wherein the first plurality of physical addresses are arranged and selected according to a prioritization.

7. The method of claim 6, wherein the prioritization dynamically changes over time.

8. The method of claim 1, wherein each of the intermediate identifiers is a name and namespace combination.

9. A system, comprising:

a central data storage device;

a plurality of servers executing a plurality of micro-services, wherein each of the servers executes a selected one of the plurality of micro-services, the plurality of servers being coupled to the central data storage device;

wherein each of the plurality of micro-services registers with the central data storage device by determining a mapping between intermediate identifiers that identify selected ones of the micro-services and physical addresses of the servers;

wherein at least one of the physical addresses is dynamically updated based upon operational changes to the servers or based upon registration of an additional server.

10. The system of claim 9, wherein the plurality of micro-services include a first micro-service and a second micro-service, and further comprising:

a customer device that requests execution of the first micro-service, the first micro-service programmatically calling the second micro-service, the first micro-service accessing the second micro-service via a first intermediate identifier that identifies the second micro-service;

wherein the first micro-service accesses the mapping and obtains a physical address of a server that executes the second micro-service using the first intermediate identifier;

wherein the customer device executes the second micro-service by utilizing the physical address obtained from the mapping.

11. The system of claim 9, wherein the physical addresses are URLs.

12. The system of claim 9, wherein the mapping further maps each of the intermediate identifiers to one or more of:

a HTTP method, an input consumption by a selected micro-service, an output production by a selected micro-service, and a version number.

13. The system of claim 9, wherein the mapping is between a selected intermediate identifier and a plurality of physical addresses.

14. The system of claim 13, wherein the plurality of physical addresses are arranged and selected according to a prioritization.

15. The system of claim 14, wherein the prioritization dynamically changes over time.

16. The system of claim 9, wherein each of the intermediate identifiers is a name and namespace combination.