The document provides an introduction and overview of Apache NiFi and its architecture. It discusses how NiFi can be used to effectively manage and move data between different producers and consumers. It also summarizes key NiFi features like guaranteed delivery, data buffering, prioritization, and data provenance. Finally, it briefly outlines the NiFi architecture and components as well as opportunities for the future of the MiniFi project.
Can put NiFi on a Gateway server but probably don’t want to mess with a UI on ever single one
Maybe not best fit
Let me get the key parts of NiFi close to where data begins and provide bidrectional communication
NiFi lives in the data center. Give it an enterprise server or a cluster of them.
MiNiFi lives close to where data is born and may be a guest on that device or system
Introduce the architecture of NiFi, describe major system components, and describe the single node and clustering models.
Framework – put a new wrapper on the framework, or in maven terms, we kept the underlying modules and wrote minifi-framework-core replacing nifi-framework-core
Talking about MiNiFi-Java, Cpp version also exists
Initiates with ./bin/nifi.sh start
user, only need bootstrap and config.yml
nifi.properties and flow.xml are implementation details
1 of the main differences with NiFi
Warm Redeploys
Think NiFi Process Groups but MiNiFi Agents
Kafka
Reads events in memory and write to distributed log