Informatica Axon Competitors and Alternatives
Read reviews of Informatica Axon competitors and alternatives
Data Architect at NAMM
Jan 30, 2020
Enabled us to centralize a tremendous amount of data into a common standard, and uniform reporting has decreased report requests
What is our primary use case?We're a medical company and we have our own source systems that process claims from multiple organizations or health plans. In our world, there are about 17 different health plans. Within each of those health plans, the membership, or the patients, have multiple lines of businesses, and the way our company is organized, we're in three different markets with up to 17 different IPAs (Independent Physician Associations). While that is a mouthful, because of data governance, and our having own data governance tool, we understand those are key concepts and that is our use case: so that everybody in… more »
Pros and Cons
- "The biggest benefit with erwin DI is that I have a single source of truth that I can send anybody to. If anybody doesn't know the answer we can go back to it. Just having a central location of business rules is good."
- "The solution gives us data lineage which means we can see an impact if we make a change. The ability for us to have that in this company is brilliant because we used to have 49 data stewards from some 23 different groups within six major departments. Each one of those was a silo unto itself. The ability to have different glossaries — but all pointed to the same key terms, key concepts, or key attributes — has made life really simple."
- "The fact that I sometimes have to go in and out of different applications, even though it's all part of the whole erwin suite, perhaps means it could be architected a little bit better. I think they do have some ideas for improvements there."
- "There was a huge learning curve, and I'd been in software development for most of my career. The application itself, and how it runs menus and screens when you can modify and code, is complex. I have found that kind of cumbersome."
What other advice do I have?Our first goals were data literacy and data as an asset. Those were our two big, ultimate goals three years ago. Data literacy turned out to be 10 times more important than a data warehouse. We could look at existing data sets and, just by educating people, it gave them an advantage almost immediately. The fact that the data governance was able to put a framework around data literacy helped us focus on the right answer, even if it wasn't the first one given. In other words, sometimes we'd have the same answer three or four times, and it would shift until we nailed it. But without governance…
Solution Architect at a financial services firm with 10,001+ employees
Real UserTop 10
Dec 31, 2020
Solid multi-ingestion tool but with poor exception handling
What is our primary use case?Zaloni is actually a big data platform management tool. It is extensively used. They have different connectors. You can start ingesting your batch and you can also use real-time streaming, but we haven't used that component. We have used it mostly for batch ingestions. It's not a single product. It has multiple pieces within itself. I think most of them are plug-and-play. We are using the enterprise version of Zaloni.
Pros and Cons
- "You can create a lot of ingestions based on the file levels or based on the time."
- "The major pain point with Zaloni is that their exception handling is not good. If any event happens, it doesn't tell you at which point it failed and it doesn't tell the operations team how they should take corrective actions unless you call Zaloni and then identify the issues. That is one issue."
What other advice do I have?I would recommend Zaloni. But before choosing they should evaluate different options so they know which one is better. Even though we have similar products, some products are good in one aspect, some are not good in others. Take the example of Informatica. Informatica is very good for database warehousing platforms. But when it comes to big data and when you have to input the data into big data then it has a lot of difficulties. Then I had to use another component that was better in handling the data. So it's based on the need. What is your objective and where are you pulling out the data? If…
Sr Manager - Enterprise Data Office at a healthcare company with 10,001+ employees
Shows the whole history of data elements, though connectors could be improved
What is our primary use case?I've been working with multiple companies, but with two of the companies we have been using Collibra mostly for data governance. With these companies, our use case is all about metadata governance, lineage, and data-related policy management. We're doing policy management directly inside Collibra and we're also using it for issue management on the analytics side. If someone has a data concern, they just call me in and then put that concern into Collibra as a front-end UI for the data stewards and data scientists, and we start processing them.
Pros and Cons
- "I like the lineage feature the most because I don't think there's any other tool that actually depicts the data flow from multiple sources and the connectivities between every data element inside those sources."
- "The connectors are not very sophisticated. They can do, for example, Informatica and Tableau, but the connectors themselves could be improved."