The Apache NiFi project as a whole (including MiNiFi) is all about routing getting the right data to the right place.
170 different actions bundled by default
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
Same page with terminology
The Apache NiFi project as a whole (including MiNiFi) is all about routing getting the right data to the right place.
The Apache NiFi project as a whole (including MiNiFi) is all about routing getting the right data to the right place.
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
Aggregator vs. Agent
Pi -> AWS NiFi
NiFi 0.7.0 is ~600mb, but most of that is UI and components
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
MiNifI packaged components ~20mb
Initiates with ./bin/nifi.sh start
user, only need bootstrap and config.yml
nifi.properties and flow.xml are implementation details
Since it uses the same underlying framework, MiNiFi is extensible exactly like NiFi
NiFi 0.7.0 has 155 different processors to chose from
Pub/sub communication (ie. Kafka, MQTT)
Endpoint delivery (ie. HDFS, HBase)
Format validation/transformation (ie. JSON, XML)
Yandex Language Translation
Nifi.properties -> omitted for defaults
Truck: need to be notified of high temp or humidity
Now that we’ve covered the basic architecture of MiNiFi we can talk about 0.0.1