Our primary use case is to help our clients integrate all of their data solutions and what they expected through MANTA Flow having a panoramic view of their data. They can see the pipelines, where the data comes from, where the data goes, and where it is consumed. These transformations are happening in the pipeline.
Very Powerful, with cloud based scalability, and highly efficient for both business and technical teams
What is our primary use case?
What is most valuable?
You can use this engine from MANTA Flow to show in the data catalog your lineage. So if you search for some datasets or data assets, you can see from where or to where that data is going or coming. The business can see and realize from which system he's consuming that data. I believe it is very powerful. And for technicians, you can see the impact analysis, you can compare versions. So you can see some revisions against some of the oldest ones. You can compare and see which pipelines were updated between the both of them. I think it is very helpful to both sides, the technical and business teams.
What needs improvement?
I had some difficulties, trying to use the direct link which is metadata through files that you can upload to MANTA Flow and you can just say from there where that data is going. But we just figured out that sometimes, depending on the level of the granularity that if you want to link the object, you can not. For example, if you want to link the objects just by schema, sometimes it does not work. So you need to scroll down and link each table. Sometimes the table level does not work, and you need to go deeper and go to link column to column. We figured out that this was a bug in MANTA Flow, and we talked to them and I think they were fixing it. But in our case, we just realized that if we could link the objects at the lowest level possible, it would work. I was trying to develop, right now, some kind of automation to compare the listed revision that I have in MANTA Flow with some other revision. And I would like to do it in an automatic way. I would like to have some kind of API where I could call this object and the revision that I want and the same object and another revision that I wanted to compare with. And I could not see it as some API in MANTA Flow, and we have this feature on the user interface. I think it would be very powerful because if you want to automate just warn the data owners the structures were updated by looking at the object level, and send an email to these owners to see if that change makes sense.
For how long have I used the solution?
I have been using MANTA Flow for the past six months more or less.
What do I think about the stability of the solution?
I would rate the stability a seven on a scale of one to ten.
What do I think about the scalability of the solution?
The scalability is good because this can be achieved in the cloud.
How are customer service and support?
Technical support is doing an interesting job as it evolves.
How would you rate customer service and support?
Positive
How was the initial setup?
When it comes to implementation, I believe it will depend on the size and the number of different data sources, BI tools, and integration tools that you are using. Because you need to expand the number of people that you need to implement and maintain these pipelines.
What other advice do I have?
I would encourage individuals to start small and choose maybe some data sources and data integration tools that you already have some native connectors, and then start to expand it to those ones that you will need to build some customized connectors. I would rate MANTA Flow an eight out of ten.
Which deployment model are you using for this solution?
On-premises
