Some positive comments here on NiFi. I found it to not be that great. I used it 4 or so years ago but things may of changed. 1) you get a big canvas which is

Some positive comments here on NiFi. I found it to not be that great. I used it 4 or so years ago but things may of changed. 1) you get a big canvas which is just drag and drop. The canvas can get huge and scrolling across the screen etc 2) leads on from previous, vary easy to go and accidentally drag something to the wrong place or stop a paticular flow 3) some flows get stuck then a pain to restart 4) it was hard to version and do the dev / test / prod deployment. You got a huge XML file if you export the flows which do not diff 5) it’s hard to test. You can create your own processors and unit test them then deploy the jars but that doesn’t seem the nifi way. Instead you use the built in processors and glue them together. They are configuration essentially, configured in a GUI so you can’t test them programmatically. You can use groovy scripts support which is built in but you hit the same issue, how do you test inside nifi 6) no multi tenant or weak acls. Bit of a pain if want a shared nifi server as you have one massive canvas I can see the appeal if a team had their own nifi instances but I find it still a cludge and writing a small specific app / microservice far simpler and more efficient for ETL pipelines etc