← Directory

Apache-NIFI

Apache NiFi supports powerful and scalable directed graphs of data routing, transformation, and system mediation logic.

  • Productivity
Apache NiFi supports powerful and scalable directed graphs of data routing, transformation, and system mediation logic.

Platform availability

Available on 1 of 6 install platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)

Also on Docker Hub and GitHub

Health score

7/100 Low

Maintained
0last commit 2049 days ago
Popular
00 GitHub stars
Easy to install
201 install platform, Docker image
Light to run
208 GB minimum RAM, runs on ARM
How is this calculated?

A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). Factors without data are left out and the rest are rescaled.

Availability: platform listings confirmed today, links checked 6 days ago

GitHub stars
0
Open issues
0
Last commit
2021-02-24
Activity
stale

Checked 7 days ago - source: GitHub (DanRegalia/NIFI-Unraid)

Resources & Compatibility

Minimum requirements: 8 GB RAM, 8 CPU core(s). ARM (e.g. Raspberry Pi) is supported.

Checked 7 days ago - source: Docker Hub image tags and published docs

First-install notes

No first-install notes yet.

Alternatives (1)

Checked 4 days ago - source: AlternativeTo

Common questions

How do self-hosters usually back up or version-control NiFi flows?

The thread discusses using a NiFi Registry for versioning, or backing up and sending flow configuration files such as flow.json.gz to git. It also notes that there appears to be a git integration.

What security and authorization options does NiFi support for self-hosted use?

NiFi supports HTTPS with configurable authentication strategies, multi-tenant authorization and policy management, and encrypted communication using TLS and SSH.

What are common pitfalls when adopting and self-hosting NiFi?

For bespoke ad hoc work, use script processors but rely on common functions and libraries to avoid creating new deployment dependencies.

What operational issues should I check when NiFi pipelines are failing?

Check for port conflicts, queue backpressure, JVM memory pressure, and cluster instability when pipelines are not healthy.

Answers sourced from nifi.apache.org, www.e-no.co, www.reddit.com, www.reddit.com

Community

Collected yesterday - public community threads