Suspect....free trial without any mention of price. Makes no sense.
Also: no personal details on the homepage about the team and the ownership structure. Why should I share my data with somebody who doesn't share his.
DataJet – Fully managed Apache NiFi as a service. Visual Data flows without code
21–24 of 24 posts
Re: DataJet – Fully managed Apache NiFi as a service. Visual Data flows without code
#22Is NiFi that bad to run by yourself?
No, I run a small nifi cluster (8 nodes) on aws and it is very stable in my opinion. You need a zookeeper cluster, which is also very stable.
I made the setup scalable, which is a nice feature, but you can do without it. Nifi has no problems being scaled down or up.
The biggest problem is when your zookeeper cluster goes down. Nifi happily goes one with processing, but now it can't update the state of its processors, so it keeps doing the same stuff over and over again. Perhaps this is already fixed, dunno. I shut the cluster down now, if I detect zookeeper is down and then start everything up again if zookeeper is ok. But this happens about once in the two year.
It can also talk with LDAP, which is nice in corporate organizations. And it has a shit ton of processors, that do the work for you. If you have lots of etl flows, I can warmly advice to have a look at it.
I update it once every 6 months or so, it is an internal tool. I haven't got a hassle with that yet.
Re: DataJet – Fully managed Apache NiFi as a service. Visual Data flows without code
#23Suspect....free trial without any mention of price. Makes no sense.
This is standard for enterprise software, because there is no fixed price.
Re: DataJet – Fully managed Apache NiFi as a service. Visual Data flows without code
#24Some 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