Apache NiFi has a well-thought-out architecture. Once data is fetched from external sources, it is represented as FlowFile inside Apache NiFi architecture.
NiFi Architecture
Here are key components of NiFi architecture
| Nifi Component | Description |
|---|
| FlowFile | FlowFile is original data with meta-information attached to it. It allows you to process not only CSV or other record-based data, but also pictures, videos, audio, or any other binary data. |
| Flowfile processor | Performs the work which acts as a building block of data flow in NiFi. |
| Flow controller | Keeps a record of how processes are connected. It manages the threads and allocations thereof which all processes use. |
| Web Server | Web server hosts NiFi’s HTTP-based commands and API. |
| Extension | There are many types of NiFi extensions which operate and execute within the JVM. |
| Connection | Acts as a linkage between processors that contain a queue and relationship(s) which affects where data is routed. |
| Back Pressure | Stop the system of becoming overrun by controlling the quantity or data size of flow files that can be stored in the queue. |
| Process Group | A process group is a set of processes and their connections, which receives and send data with the help of ports. |
| Flowfile Repository | In the FlowFile Repository, NiFi keeps track of the state of what details it has about a given FlowFile which is active in the flow. |
| Content Repository | The Content Repository is an area where the actual content bytes of a given FlowFile exist. |
Provenance Repository
Source: https://www.guru99.com/ | The Provenance Repository is an area where all provenance event data is gathered.
|
