Nanoservice computing and architecture

Patent metadata

Field	Value
Publication number	US-12379938-B2
Application number	US-202217822294-A
Country	US
Kind code	B2
Filing date	Aug 25, 2022
Priority date	Aug 25, 2022
Publication date	Aug 5, 2025
Grant date	Aug 5, 2025

Abstract

A nanoservice architecture allows a service to include multiple functions or features along with a common skeleton code. Each of the nanoservices in a service may be configured using a common configuration file. The configuration file may include a portion that configures requirements or resources common to all nanoservices and other portions that are specific to associated nanoservices.

First claim

What is claimed is:

1. A method, comprising:
deploying a service that includes a skeleton component, a first nanoservice and a second nanoservice to a node operating in an environment, wherein the skeleton component includes skeleton code common to and used during execution of the first nanoservice and the second nanoservice;
instantiating the first nanoservice and the second nanoservice on the node;
processing a configuration file included in the skeleton code, wherein the configuration file includes a first portion that is relevant to the first nanoservice, a second portion that is relevant to the second nanoservice, and a third portion that is relevant to both the first nanoservice and the second nanoservice;
configuring the first nanoservice and the second nanoservice in accordance with the configuration file;
executing the first nanoservice and the second nanoservice on the node; and
after deploying the service and executing the first and second nanoservices on the node, adding a third nanoservice to the service without adding to the skeleton code of the service, wherein the skeleton code is common to and used during execution of the third nanoservice,
wherein the service is configured such that each of the first nanoservice, the second nanoservice, and the third nanoservice can be removed from the service without starting another instance of the service.

2. The method of claim 1 , wherein the configuration file includes an instantiation portion for instantiating the first nanoservice and the second nanoservice.

3. The method of claim 1 , wherein only the first nanoservice processes the first portion of the configuration file and only the second nanoservice processes the second portion of the configuration file.

4. The method of claim 1 , wherein the service processes the third portion, wherein the third portion configures at least one of a database and logging for both the first nanoservice and the second nanoservice.

5. The method of claim 1 , wherein the first nanoservice and the second nanoservice are instantiated as separate threads inside an operating system process.

6. The method of claim 1 , further comprising caching, by a data handling function, data from a database for consumption by the first nanoservice and the second nanoservice.

7. The method of claim 1 , wherein the service comprises a nanoservice overhead common to the first nanoservice and the second nanoservice.

8. The method of claim 1 , further comprising starting, stopping, and/or restarting the first nanoservice and the second nanoservice at the same time.

9. The method of claim 1 , wherein the skeleton code includes code to start the first and second nanoservices, handle configurations and modifications related to the first and second nanoservices, and shut down the nanoservices.

10. The method of claim 1 , wherein the first nanoservice and the second nanoservice are part of an application and are related in function or purpose.

11. The method of claim 10 , wherein the first nanoservice and the second nanoservice operate independently of each other.

12. The method of claim 1 , wherein the service is implemented in a node operating in an environment, wherein the node is one of multiple nodes operating in the environment and wherein the multiple nodes each comprise a service that includes one or more nanoservices.

13. The method of claim 12 , wherein further comprising a forklift or an autonomous device, wherein the node is part of the forklift or the autonomous device.

14. A non-transitory storage medium having stored therein instructions that are executable by one or more hardware processors to perform operations comprising:
deploying a service that includes a skeleton component, a first nanoservice and a second nanoservice to a node operating in an environment, wherein the skeleton component includes skeleton code common to and used during execution of the first nanoservice and the second nanoservice;
instantiating the first nanoservice and the second nanoservice on the node;
processing a configuration file included in the skeleton code, wherein the configuration file includes a first portion that is relevant to the first nanoservice, a second portion that is relevant to the second nanoservice, and a third portion that is relevant to both the first nanoservice and the second nanoservice;
configuring the first nanoservice and the second nanoservice in accordance with the configuration file;
executing the first nanoservice and the second nanoservice on the node; and
after deploying the service and executing the first and second nanoservices on the node, adding a third nanoservice to the service without adding to the skeleton code of the service, wherein the skeleton code is common to and used during execution of the third nanoservice,
wherein the service is configured such that each of the first nanoservice, the second nanoservice, and the third nanoservice can be removed from the service without starting another instance of the service.

15. The non-transitory storage medium of claim 14 , wherein the configuration file includes an instantiation portion for instantiating the first nanoservice and the second nanoservice, wherein only the first nanoservice processes the first portion of the configuration file and only the second nanoservice processes the second portion of the configuration file.

16. The non-transitory storage medium of claim 14 , wherein the service processes the third portion, wherein the third portion configures at least one of a database and logging for both the first nanoservice and the second nanoservice, wherein the first nanoservice and the second nanoservice are instantiated as separate threads inside an operating system process.

17. The non-transitory storage medium of claim 14 , further comprising caching, by a data handling function, data from a database for consumption by the first nanoservice and the second nanoservice.

18. The non-transitory storage medium of claim 14 , wherein the service further comprises a nanoservice overhead common to the first nanoservice and the second nanoservice and includes the skeleton code common to the first nanoservice and the second nanoservice, the operations further comprising stopping and/or restarting the first nanoservice and the second nanoservice at the same time.

19. The non-transitory storage medium of claim 14 , wherein the first nanoservice and the second nanoservice are part of an application and are related in function or purpose, wherein the first nanoservice and the second nanoservice operate independently of each other, wherein the service is implemented in a node operating in an environment, and wherein the node is one of multiple nodes operating in the environment and wherein the multiple nodes each comprise a service that includes one or more nanoservices.

Assignees

• Dell Products Lp

Inventors

• Caron Eric L
• Bruno Eric

Classifications

• G06F9/44521

  Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading · CPC title

• G06F9/44505 Primary

  Configuring for program initiating, e.g. using registry, configuration files · CPC title

• G06F8/60 Primary

  Software deployment · CPC title