Qlik Replicate vs SnapLogic comparison

"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."

"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."

"The most valuable features of Qlik Replicate are its CDC performance and trigger functions. CDC feature is important to the financial industry."

"The most useful functions of Qlik Replicate are the data manipulation to transformations."

"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."

"Great with replicating and updating records."

"Support has been great."

"It enables us to transform data at the latest stage rather than in ETL loads, so it's more ELT which is one of the advantages. It is also in near real-time, which brings significant advantage for our embedded analytics approach."

"By using snaps instead of functions in code, you can see the building blocks of the integration visually. This helps a lot."

"SnapLogic is an IPA tool that leverages a low code environment to connect to multiple sources, extract data, and store it in Azure data lake."

"It's more developer-friendly, and development can be done at a faster phase."

"I found SnapLogic valuable and what I found most valuable about it was its ETL feature. I also found its automation feature valuable. It can be used for automating manual activities. It can be used as a middleware for certain transactional data processing and minimal datasets and ETL activities."

"The solution is easy to implement and easy to use. It's basically just drag and drop."

"The initial setup is very straightforward."

"What I found most valuable in SnapLogic is the ETL feature, particularly the Transform Snap Pack, for example, any kind of reading or writing on Transform Snaps. Other than that, all the third-party connectivity tools such as the SAP Snap Pack, Salesforce Snap Pack, Workday Snap Pack, even the ServiceNow Snap Pack, I find all those are pretty useful in SnapLogic."

"You can use other languages, such as Python, and easily connect to other systems."

"The solution's flexibility to work with APIs should also be improved since it is very weak in working with APIs."

"Support for this product is not great. It needs to be improved."

"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."

"It's not possible to replicate the QVC files in data analytics."

"The product should improve its licensing limitation."

"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."

"We would like to see more details in messages about errors with the system."

"It needs some more snaps. I would like to see some of the features be changed in some of the snaps."

"There is room for improvement with APM management and how task execution looks."

"SnapLogic sits somewhere in the middle. It doesn’t offer enough easy canned integrations for its users like some of the easier to use integration apps."

"I would like to see more performance-related dashboards, ones that display the cost of a pipeline, for instance. Also, it would be helpful to have management dashboards for overseeing pipelines and connections."

"Ultra Pipelines provides real-time ingestion but it needs some adjustment."

"SnapLogic should have some inbuilt protocol mechanism in order to speed up."

"We'd like there to be more ways for users to get more comfortable and have more experience with the solution to make it easier to use."

"What could be improved in SnapLogic is that it was not capable in terms of processing a large number of datasets, but at that point, SnapLogic was evolving. It didn't give a lot of Snaps. I heard recently there are a lot of Snaps getting added and the solution was being enhanced, particularly to connect different data sources. When I was working with SnapLogic six months to one year back, I faced the issue of it not being capable of handling a huge volume of datasets or didn't have much of Snaps, and that was the drawback. If there is any large number of data sets, that's based on or depends on your configuration. If it is a huge volume of data, other traditional ETL tools such as Informatica and Talend can process millions and billions of records, while in SnapLogic, the Snaplex fails or it returns an error in terms of processing that huge volume of data. Informatica, Talend, or any other ETL tool can run for hours in terms of jobs, while SnapLogic jobs fail when the threshold is reached. SnapLogic isn't able to withstand processing, but I don't know if that's still an issue at present, because the solution is getting enhanced and it's been more than six months to one year since I last worked with SnapLogic. There are now a lot of Snaps getting added to the solution, and if it can overcome the limitations I mentioned, SnapLogic could be the go-to tool because currently, it's not being used as much in organizations. It's being used comparatively less compared to other retail tools."

"On a scale from one to ten, where one is cheap, and ten is expensive, I rate Qlik Replicate's pricing a nine out of ten."

"Qlik Replicate is not expensive, compared to GoldenGate."

"Overall, Qlik is an expensive solution. You need to pay for all additional features that you would like to use."

"Unlike Azure, where you pay based on consumption, Qlik Replicate seems to charge per endpoint."

"Qlik Replicate is mainly suited for large companies. However, it is too costly for small businesses. Its pricing is high."

"Pricing for this solution is very reasonable."

"From the ROI perspective, the price is extremely high"

"SnapLogic's price is high compared to the other tools available in the market."

"When comparing it with solutions like Apigee or MuleSoft, it still offers better value."

"SnapLogic is not expensive. It's reasonably priced."

"They have pricing/usage tiers that are easy to move up or down."

"By scaling the solution incrementally the cost is controlled and more beneficial to the client."

"The license model is based on consumption."

"It is a higher initial cost than other easy-to-use integration apps."