Difference between revisions of "Data Flow"
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
For all workflows, it must involve time, which provides an implicit ordering structure. In the world of [[ | For all workflows, it must involve time, which provides an implicit ordering structure. In the world of [[PKC]], we may leverage this ordering property to orchestrate [[data flow]]s. | ||
Since Data can be thought of as Page, File, or Services, we will explain how to use this generalized abstraction to manage data [[workflow]]s: | Since Data can be thought of as Page, File, or Services, we will explain how to use this generalized abstraction to manage data [[workflow]]s: | ||
Latest revision as of 08:38, 9 September 2021
For all workflows, it must involve time, which provides an implicit ordering structure. In the world of PKC, we may leverage this ordering property to orchestrate data flows.
Since Data can be thought of as Page, File, or Services, we will explain how to use this generalized abstraction to manage data workflows:
PageFlow
PKC is designed as a symmetric data container to enable convenient deployment and operation of data workflow. Another way to think about the PKC is how it uses web pages to connect data, therefore, one can think of it as PageFlow.
FileFlow
Once a image, video, sound file, or a file that represents the compressed data in a directory structure, the entire file is thought of as a unit of abstraction, to be submitted in a FileFlow.
ServiceFlow
To manage a distributed system, services are given unique names in a network environment, so that every computing service can be identified in a ServiceFlow.