Computer architectures using shared storage

• US 9,690,839 B2
• Filed: 01/05/2015
• Issued: 06/27/2017
• Est. Priority Date: 03/30/2009
• Status: Active Grant

• Current Assignee: The Boeing Co.
• Original Assignee: The Boeing Co.
• Inventors: Stone, Kevin A., Peters, Marc A., Kuehn, Dennis L., Bettger, David D.
• Primary Examiner(s): Tsai, Henry
• Assistant Examiner(s): Hassan, Aurangzeb
• Application Number:
  US14/589,521
• Publication Number:
  US 20150143001A1
• Time in Patent Office: 904 Days
• Field of Search: None
• CPC Class Codes: G06F 12/0813 with a network or matrix configuration
• CPC Class Codes: G06F 13/4221 being an input/output bus, e.g. ISA bus, EISA bus, PCI bus, SCSI bus
• CPC Class Codes: G06F 16/176 Support for shared access to files; File sharing support
• CPC Class Codes: G06F 16/28 Databases characterised by their database models, e.g. relational or object models
• CPC Class Codes: G06F 3/0607 by facilitating the process of upgrading existing storage systems, e.g. for improving compatibility between host and storage device
• CPC Class Codes: G06F 3/0608 Saving storage space on storage systems
• CPC Class Codes: G06F 3/0655 Vertical data movement, i.e. input-output transfer; data movement between one or more hosts and one or more storage devices
• CPC Class Codes: G06F 3/067 Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]
• CPC Class Codes: G06F 3/0689 Disk arrays, e.g. RAID, JBOD
• CPC Class Codes: G06F 9/50 Allocation of resources, e.g. of the central processing unit [CPU]

Abstract

An Enterprise Service Bus (ESB) system includes a shared storage that stores data corresponding to files, a file system, and ESB infrastructure functions. The ESB system includes a metadata registry storing metadata associated with the ESB infrastructure functions, separate from the ESB infrastructure functions, and includes storage location information of the ESB infrastructure functions. The ESB system includes a processor configured to receive a request for access to the file system. The processor sends a portion of the metadata registry to a client device, the portion including a portion of the metadata and a directory structure identifying a set of the ESB infrastructure functions that the client device is authorized to access, the portion of the metadata allowing the client device to access a first infrastructure function of the set based on the storage location information. The processor further provides the first infrastructure function to the client device.

Claims

1. An Enterprise Service Bus (ESB) system comprising:

a shared storage, the shared storage storing data corresponding to files, a file system, and ESB infrastructure functions;

a metadata registry storing metadata associated with the ESB infrastructure functions, wherein the metadata is stored separately from the ESB infrastructure functions, and wherein the metadata includes storage location information of the ESB infrastructure functions; and

a processor configured to;

receive a request for access to the file system;

send a portion of the metadata registry to a client device, the portion including a portion of the metadata and a directory structure identifying a set of the ESB infrastructure functions that the client device is authorized to access, the portion of the metadata configured to enable the client device to access a first infrastructure function of the set of the ESB infrastructure functions based on the storage location information, the first infrastructure function executable by the client device to cause the client device to read a first portion of data written to the shared storage by a producer service while a second portion of data is written to the shared storage by the producer service; and

provide the first infrastructure function to the client device.

2. The ESB system of claim 1, wherein the directory structure does not identify storage location information of the set of the ESB infrastructure functions.

3. The ESB system of claim 1, wherein the client device and the producer service are configured to communicate using read after write.

4. The ESB system of claim 1, wherein the processor is further configured to write to the shared storage to modify the first infrastructure function while the client device uses the first infrastructure function, wherein modification of the first infrastructure function does not affect use of the first infrastructure function by the client device.

5. The ESB system of claim 1, wherein the processor is further configured to:

allocate storage space in the shared storage for output data of the first infrastructure function executed by the client device;

update the metadata registry to include second metadata corresponding to second storage location information that indicates the storage space; and

send the second storage location information to the client device.

6. The ESB system of claim 1, wherein the first infrastructure function provided to the client device is a stateless function, wherein the first infrastructure function is instantiated, executed, and terminated at the client device, and wherein information is not retained in the shared storage regarding use, state, or security level of the first infrastructure function.

7. The ESB system of claim 1, wherein a persistent common view of the files, the file system and the ESB infrastructure functions is provided through a virtualized layer, and wherein the metadata registry comprises information to generate the persistent common view.

8. The ESB system of claim 1, wherein the ESB infrastructure functions operate on size, location, security level, protocol, or a combination thereof, of particular data, and wherein the first infrastructure function does not operate on a data type or data content of the particular data.

9. The ESB system of claim 1, wherein the ESB infrastructure functions provide quality of service control, fault tolerance, routing, addressing, service registration, discovery functions, or combinations thereof.

10. A method comprising:

receiving, at an Enterprise Service Bus (ESB), a request for access to a file system, wherein a shared storage stores data corresponding to files, the file system, and ESB infrastructure functions;

sending a portion of a metadata registry to a client device, wherein the metadata registry stores metadata associated with the ESB infrastructure functions, the metadata stored separately from the ESB infrastructure functions, wherein the metadata includes storage location information of the ESB infrastructure functions, wherein the portion includes a portion of the metadata and a directory structure identifying a set of the ESB infrastructure functions that the client device is authorized to access, the portion of the metadata allowing the client device to access a first infrastructure function of the set of the ESB infrastructure functions based on the storage location information, the first infrastructure function executable by the client device to cause the client device to read a first portion of data written to the shared storage by a producer service while a second portion of data is written to the shared storage by the producer service; and

providing the first infrastructure function to the client device.

11. The method of claim 10, wherein the directory structure does not identify storage location information of the set of the ESB infrastructure functions.

12. The method of claim 10, wherein the client device and the producer service communicate using read after write technology.

13. The method of claim 10, further comprising writing to the shared storage to modify the first infrastructure function while the client device is using the first infrastructure function, wherein modifying the first infrastructure function does not affect use of the first infrastructure function by the client device.

14. The method of claim 10, further comprising:

allocating storage space in the shared storage for output data of the first infrastructure function executed by the client device;

updating the metadata registry to include second metadata corresponding to second storage location information identifying the storage space; and

sending the second storage location information to the client device.

15. The method of claim 10, wherein the first infrastructure function provided to the client device is a stateless function, wherein the first infrastructure function is instantiated, executed, and terminated at the client device, and wherein information is not retained in the shared storage regarding use, state, or security level of the first infrastructure function.

16. The method of claim 10, wherein a persistent common view of the files, the file system and the ESB infrastructure functions is provided through a virtualized layer, and wherein the metadata registry comprises information to generate the persistent common view.

17. A non-transitory computer readable medium comprising instructions that, when executed by a processor, cause the processor to perform operations comprising:

receiving, at an Enterprise Service Bus (ESB), a request for access to a file system, wherein a shared storage stores data corresponding to files, the file system, and ESB infrastructure functions;

sending a portion of a metadata registry to a client device, wherein the metadata registry stores metadata associated with the ESB infrastructure functions, the metadata stored separately from the ESB infrastructure functions, wherein the metadata includes storage location information of the ESB infrastructure functions, wherein the portion includes a portion of the metadata and a directory structure identifying a set of the ESB infrastructure functions that the client device is authorized to access, the portion of the metadata allowing the client device to access a first infrastructure function of the set of the ESB infrastructure functions based on the storage location information, the first infrastructure function executable by the client device to cause the client device to read a first portion of data written to the shared storage by a producer service while a second portion of data is written to the shared storage by the producer service; and

providing the first infrastructure function to the client device.

18. The non-transitory computer readable medium of claim 17, wherein the directory structure does not identify storage location information of the set of the ESB infrastructure functions.

19. A method comprising:

receiving, at an Enterprise Service Bus (ESB), a request for access to a file system, wherein a shared storage stores data corresponding to files, the file system, and ESB infrastructure functions;

allocating storage space in the shared storage for output data of a first ESB infrastructure function, of the ESB infrastructure functions, executed by a client device;

updating a metadata registry to include metadata corresponding to first storage location information that indicates the storage space;

sending the first storage location information to the client device; and

sending a portion of the metadata registry to the client device, wherein the portion includes a portion of the metadata and a directory structure identifying a set of the ESB infrastructure functions that the client device is authorized to access, the portion allowing the client device to access the first ESB infrastructure function based on second storage location information.

20. A non-transitory computer readable medium comprising instructions that, when executed by a processor, cause the processor to perform operations comprising:

receiving, at an Enterprise Service Bus (ESB), a request for access to a file system, wherein a shared storage stores data corresponding to files, the file system, and ESB infrastructure functions;

allocating storage space in the shared storage for output data of a first ESB infrastructure function, of the ESB infrastructure functions, executed by a client device;

updating a metadata registry to include metadata corresponding to first storage location information that indicates the storage space;

sending the first storage location information to the client device; and

sending a portion of the metadata registry to the client device, wherein the portion includes a portion of the metadata and a directory structure identifying a set of the ESB infrastructure functions that that the client device is authorized to access, the portion allowing the client device to access the first ESB infrastructure function based on second storage location information.