Archite Data Flow Architecture
Archite Data Flow Architecture
In data flow architecture, the whole software system is seen as a series of transformations
on consecutive pieces or set of input data, where data and operations are independent of
each other. In this approach, the data enters into the system and then flows through the
modules one at a time until they are assigned to some final destination (output or a data
store).
The connections between the components or modules may be implemented as I/O stream,
I/O buffers, piped, or other types of connections. The data can be flown in the graph
topology with cycles, in a linear structure without cycles, or in a tree type structure.
The main objective of this approach is to achieve the qualities of reuse and modifiability. It
is suitable for applications that involve a well-defined series of independent data
transformations or computations on orderly defined input and output such as compilers
and business data processing applications. There are three types of execution sequences
between modules−
Batch sequential
Process control
AppSumo
Batch Sequential
Batch sequential is a classical data processing model, in which a data transformation
subsystem can initiate its process only after its previous subsystem is completely through
−
The flow of data carries a batch of data as a whole from one subsystem to another.
It is applicable for those applications where data is batched, and each subsystem
reads related input files and writes output files.
Advantages
Disadvantages
The connections between modules are data stream which is first-in/first-out buffer that
can be stream of bytes, characters, or any other type of such kind. The main feature of
this architecture is its concurrent and incremented execution.
Filter
Active filter
Active filter lets connected pipes to pull data in and push out the transformed data. It
operates with passive pipe, which provides read/write mechanisms for pulling and
pushing. This mode is used in UNIX pipe and filter mechanism.
Passive filter
Passive filter lets connected pipes to push data in and pull data out. It operates with active
pipe, which pulls data from a filter and pushes data into the next filter. It must provide
read/write mechanism.
Advantages
Provides simplicity by offering clear divisions between any two filters connected by
pipe.
Disadvantages
Does not provide a way for filters to cooperatively interact to solve a problem.
Difficult to configure this architecture dynamically.
Pipe
Pipes are stateless and they carry binary or character stream which exist between two
filters. It can move a data stream from one filter to another. Pipes use a little contextual
information and retain no state information between instantiations.
Explore our latest online courses and learn new skills at your own pace. Enroll and
become a certified expert to boost your career.
AppSumo
Types of Subsystems
A process control architecture would have a processing unit for changing the process
control variables and a controller unit for calculating the amount of changes.
Sensor − Obtains values of process variables pertinent to control and can be used
as a feedback reference to recalculate manipulated variables.