End-to-end event flows that contain file locations
A method for end-to-end event flows includes storing a file associated with a source event at a source storage location in a source edge device, uploading the file to a cloud device, storing the file at a cloud storage location, generating a cloud event by changing a file path referenced in the source event to point to the cloud storage location of the file, and transferring the cloud event to the cloud device. The method includes transferring the cloud event to a destination edge device, downloading the file to the destination edge device, generating a destination event by changing the file path referenced in the cloud event to point to a destination storage location of the file, publishing an availability of the file in the destination edge device to multiple destination subscribers, and transferring the file from the destination storage location to one or more destination subscribers.
1. A method for end-to-end event flows that contain file locations comprising:
storing a data file associated with a source event file at a source storage location in a source edge device, wherein (i) the source edge device provides an entry point into a cloud, and (ii) the source event file indicates that the data file is to be made available to a plurality of destination subscribers;
uploading the data file from the source edge device to a cloud device, wherein the cloud device is within the cloud;
storing the data file at a cloud storage location in the cloud device;
generating a cloud event file by changing a file path referenced in the source event file in the source edge device to point to the cloud storage location of the data file in the cloud device;
transferring the cloud event file from the source edge device to the cloud device;
transferring the cloud event file from the cloud device to a destination edge device, wherein the destination edge device provides an exit point from the cloud;
downloading the data file from the cloud device to the destination edge device;
generating a destination event file by changing the file path referenced in the cloud event file to point to a destination storage location of the data file in the destination edge device;
publishing an availability of the data file in the destination edge device to a plurality of destination subscribers in response to the destination event, wherein the plurality of destination subscribers are outside the cloud; and
transferring the data file from the destination storage location to one or more of the plurality of destination subscribers.
2. The method according to claim 1 , further comprising:
routing the source event file to a source streamer in the source edge device.
3. The method according to claim 2 , further comprising:
detecting that the data file is associated with the source event file using the source streamer.
4. The method according to claim 3 , further comprising:
triggering the uploading of the data file from the source edge device to the cloud device in response to the detecting by the source streamer.
5. The method according to claim 4 , further comprising:
detecting a completion of the uploading of the data file from the source edge device to the cloud device, wherein the generating of the cloud event file in the source edge device is in response to the completion.
6. The method according to claim 1 , further comprising:
publishing an availability of the data file in the cloud device to a plurality of cloud subscribers in response to the cloud event file, wherein the cloud subscribers are within the cloud; and
transferring the data file from the cloud storage location to one or more of the plurality of cloud subscribers, wherein the plurality of cloud subscribers are within the cloud.
7. The method according to claim 1 , further comprising:
detecting that the data file is associated with the cloud event file using a cloud streamer in the cloud device.
8. The method according to claim 7 , further comprising:
triggering the downloading of the data file from the cloud device to the destination edge device in response to the detecting by the cloud streamer.
9. The method according to claim 8 , further comprising:
sending the cloud event file to a destination streamer in the destination edge device.
10. The method according to claim 9 , wherein the destination streamer publishes the availability of the data file in the destination edge device to the plurality of destination subscribers.
11. The method according to claim 1 , wherein the cloud device is separate from the source edge device and the destination edge device, and the source edge device is separate from the destination edge device.
12. A method for end-to-end event uploads that contain file locations comprising:
storing a data file associated with a source event file at a source storage location in a source edge device, wherein the source edge device provides an entry point into a cloud;
uploading the data file from the source edge device to a cloud device, wherein the cloud device is within the cloud;
storing the data file at a cloud storage location in the cloud device;
generating a cloud event file by changing a file path referenced in the source event file in the source edge device to point to the cloud storage location of the data file in the cloud device;
transferring the cloud event file from the source edge device to the cloud device;
publishing an availability of the data file in the cloud device to a plurality of cloud subscribers in response to the cloud event file, wherein the plurality of cloud subscribers are within the cloud; and
transferring the data file from the cloud storage location to one or more of the plurality of cloud subscribers.
13. The method according to claim 12 , further comprising:
routing the source event file to a source streamer in the source edge device.
14. The method according to claim 13 , further comprising:
detecting that the data file is associated with the source event file with the source streamer.
15. The method according to claim 14 , further comprising:
triggering the uploading of the data file from the source edge device to the cloud device in response to the detecting by the source streamer.
16. The method according to claim 15 , further comprising:
detecting a completion of the uploading of the data file from the source edge device to the cloud device, wherein the generating of the cloud event file in the source edge device is in response to the completion.
17. A method for end-to-end event downloads that contain file locations comprising:
storing a data file at a cloud storage location in a cloud device, wherein (i) the data file is associated with a cloud event file and (ii) the cloud device is within a cloud;
transferring the cloud event file from the cloud device to a destination edge device, wherein the destination edge device provides an exit point from the cloud;
downloading the data file from the cloud device to the destination edge device;
generating a destination event file by changing a file path referenced in the cloud event file to point to a destination storage location of the data file in the destination edge device;
publishing an availability of the data file in the destination edge device to a plurality of destination subscribers in response to the destination event file, wherein the plurality of destination subscribers are outside the cloud; and
transferring the data file from the destination storage location to one or more of the plurality of destination subscribers.
18. The method according to claim 17 , further comprising:
detecting that the data file is associated with the cloud event file using a cloud streamer in the cloud device.
19. The method according to claim 18 , further comprising:
triggering the downloading of the data file from the cloud device to the destination edge device in response to the detecting by the cloud streamer.
20. The method according to claim 19 , further comprising:
sending the cloud event file to a destination streamer in the destination edge device, wherein the destination streamer publishes the availability of the data file in the destination edge device to the plurality of destination subscribers.