We performed a comparison between FME and Qlik Replicate based on real PeerSpot user reviews.
Find out in this report how the two Data Integration solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."All spatial features are unrivaled, and the possibility to execute them based on a scheduled trigger, manual, e-mail, Websocket, tweet, file/directory change or virtually any trigger is most valuable."
"It has a very friendly user interface. You don't need to use a lot of code. For us that's the most important aspect about it. Also, it has a lot of connectors and few forms. It has a strong facial aspect. It can do a lot of facial analysis."
"It has standard plug-ins available for different data sources."
"The most valuable feature of FME is the graphical user interface. There is nothing better. It is very easy to debug because you can see all steps where there are failures. Overall the software is easy to optimize a process."
"We make minor subtle changes to the workbenches to improve it. We can share the workbenches. We don't have to use GitHub or anything else."
"From a technical perspective, this is an excellent product."
"Qlik Replicate stands out with its cutting-edge technology and its ability to handle diverse data management tasks. This powerful tool allows us to efficiently and swiftly load data into various data stores or destinations, while also enabling easy distribution across different endpoints. A notable feature is its capability to reload data from multiple sources by creating multiple tasks within a brief timeframe of fifteen to twenty minutes. This eliminates the need for manual intervention and ensures quick data loading from different tables."
"A valuable feature of Qlik Replicate is that you do not need ETL. It's easy to use—you choose two systems and it automatically replicates them. Even if there is no CDC available, if you insert it and update it, and there is nothing to find out, then you can use Qlik Replicate. It's a good product."
"Great with replicating and updating records."
"The main valuable feature is its real-time change data capture (CDC) capabilities, which process data with minimal latency. There is not much delay. It also performs well with batch-wise data applications."
"We use Qlik Replicate to change data capture of databases in production environments."
"The CDC and the flexibility to use QVD as a source are the most valuable features of Qlik Replicate."
"A pretty good series of connectors is one of the best features of Qlik Replicate."
"FME's price needs improvement for the African market."
"To get a higher rating, it would have to improve the price and the associated scalability. These are the main issues."
"FME can improve the geographical transformation. I've had some problems with the geographical transformations, but it's probably mostly because I'm not the most skilled geographer in-house. The solution requires some in-depth knowledge to perform some functions."
"The one thing that always appears in the community is the ability to make really easy loops to loop through data efficiently. That needs to be added at some point."
"Improvements could be made to mapping presentations."
"When you remote into it the Qlik Replicate UI a lot of times it just freezes. We set up the EC2, to allow them to go to the server and click on the Replicate icon, it just opens up and just sits there. At that point, we have to go into the EC2 and then reboot the server. This should be fixed, it is frustrating."
"The solution's flexibility to work with APIs should also be improved since it is very weak in working with APIs."
"In various scenarios, an important consideration is when we encounter issues and Qlik Replicate suggests reloading a specific table. If we face any problems or encounter errors with that table, it becomes necessary to make a change in Qlik Replicate. Performing a full reload every time is not feasible or practical. Instead, we should identify the specific issues and address them without repeating the entire reloading process. Based on this approach, we can investigate and resolve the problem by performing targeted loads from the source itself. This change aligns with my perspective and is something I would like to implement."
"Some features can also be overly dependent on each other. So, there is room for improvement."
"Support-wise, this solution is in need of improvement."
"We would like to see more details in messages about errors with the system."
"We'd like better connectivity."
"In the next release, I would like to see closer integration with data catalyst."
FME is ranked 24th in Data Integration with 5 reviews while Qlik Replicate is ranked 16th in Data Integration with 13 reviews. FME is rated 8.6, while Qlik Replicate is rated 8.2. The top reviewer of FME writes "Great for handling large volumes of data, but it is priced a bit high". On the other hand, the top reviewer of Qlik Replicate writes " Performs well with batch-wise data applications but some features can also be overly dependent on each other". FME is most compared with Alteryx Designer, Azure Data Factory, Talend Open Studio, SSIS and Informatica PowerCenter, whereas Qlik Replicate is most compared with Oracle GoldenGate, AWS Database Migration Service, Qlik Compose, Azure Data Factory and Fivetran. See our FME vs. Qlik Replicate report.
See our list of best Data Integration vendors.
We monitor all Data Integration reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
