Difference Between Apache Nifi and Apache Streampipes #1067
Replies: 1 comment 2 replies
-
Hi @Praveenstein, good question! I totally agree with your findings. In general and from a use case perspective , I'd say Nifi is a generic dataflow processing system, while StreamPipes targets the Industrial IoT space in form of a toolbox with the goal to support non-technical users in analyzing IIoT data. E.g., the pipeline editor which is closest to the graphical modeling approach of Nifi (or also NodeRED) is supplemented with other tools such as the live dashboard, data explorer, or very new additions such as standalone functions and Python support targeted at data scientists. In terms of architecture, there are probably quite a lot of differences between both tools (you have mentioned a few), e.g., the underlying data model allows to define requirements on input streams of pipeline elements, which aims at reducing modeling errors and hiding technical details of connected event streams. Hope this explains it a little bit! I'll be happy to dive deeper in case you have any questions and maybe other community members have other views ;-) |
Beta Was this translation helpful? Give feedback.
-
Just curious, i've used apache nifi a lot, just wondering how does streampipes differ?? I think streampipes architecture follows microservices pattern, apart from this any other difference, One thing that i noticed is, in apache nifi, everything is time based scheduled, so if in case i want to consume a mqtt message, i have to put a time (say every 1 min) to check for new messages, not like as soon as a message is published it will be consumed by nifi (the so called event driven strategy), can someone explain in detail, the difference, in both the underlying design principle, features, etc?? so that it could be for anybody looking for the answer in future also
Beta Was this translation helpful? Give feedback.
All reactions