We basically use it for fulfilling our data anayltics purpose. Our client is a major global semiconductor company. We use the tool to prepare data for analysis.

For real-time data integration, we have a setup with our internal configuration matching the client's name. Then there's the usual process... Qlik Replicate will capture those logs using change data capture (CDC) and then send the changes to the target in real-time.

For our source databases, we use SAP DB, AWS, SQL Server, MySQL, and PostgreSQL. Currently, we integrate with Databricks and Snowflake as well. Our main target products are Hadoop, and we're switching to Databricks. So, these are the databases or big data platforms we've integrated using Qlik Replicate.

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.

Our client is a global industrial company and needs real-time insights. With CDC, Qlik Replicate can capture changes as they happen. This allows us to process data for our platforms, where data scientists and analysts folks can generate valuable insights for management. This helps us grow the business and identify areas for improvement in real time.

It's user-friendly and has a very beautiful UI. Anyone can learn to use this tool quickly.

I wish Qlik Replicate had better built-in scheduling for initial table copies (ITCs) and full loads. Some features can also be overly dependent on each other. So, there is room for improvement. For example, one driver will not support the other source driver. 

So, it would be helpful if Qlik was clearer about driver versions, such as which ones work or don't work with specific sources. 

Another area of improvement is that full loads could be a bit faster. A tool like Informatica has both good replication and scheduling features.

I have been using it for more than three years. 

It's about 90% stable. Occasionally, when very huge amounts of data arrive simultaneously, we might see some latency. Otherwise, it's quite reliable and stable.

Scalability depends entirely on our configuration. We can allocate enough resources to ensure it scales according to our needs. 

In terms of Qlik Replicate's performance with change data capture (CDC), I find it quite good.

Our company size is  probably upper-medium in size within the US.

Qlik doesn't connect you directly to a support person. They have a help desk system where you submit a ticket with details about your issue. They'll ask follow-up questions, and you provide answers. They do provide solutions, but it can take some time.

So, there is room for improvement in terms of response time. 

Neutral

I have used tools like Azure Data Factory. Compared to others, Qlik Replicate is more user-friendly. 

However, a tool like Azure Data Factory supports a wider range of endpoints. If you need SAP S/4 HANA integration, be aware that licensing costs can be an additional factor on top of the core Qlik Replicate pricing. 

Also, it's worth noting that Qlik Replicate might not be ideal for replicating to SaaS applications – it's better suited for database-to-database scenarios.

It's easy to deploy. In our organization, we use Git and Jenkins to manage deployments.

It will need 24/7 support. The deployment took us about four hours. We generally need at least a team of five to six people for both maintenance and deployment.  

The pricing could be better. Unlike Azure, where you pay based on consumption, Qlik Replicate seems to charge per endpoint. It doesn't necessarily scale well based on how much data you actually process.

The pricing might be around $45,000. It is just a general estimate because my focus is on analysis and deployment.

Overall, I would rate the solution a seven out of ten. 

Be aware that the initial setup and configuration can be a bit complex. However, once it's stable, it's relatively easy to maintain and monitor. Qlik Replicate's strength is real-time change data capture (CDC), so if that's important for you, it's a good option.

Qlik Replicate is used when a company wants to make some sort of universal bus, a data chain where you have a continuous feed of data flowing in from source to target. The solution helps you hook in that data over the bridge at any time or granularity.

The CDC and the flexibility to use QVD as a source are the most valuable features of Qlik Replicate.

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

Qlik Replicate has been in the market for the last three years. There would be a couple of resources with more than two years of experience working with the solution and others with less than that.

While deploying an expensive enterprise product like Qlik Replicate, you need to give your customers end-to-end coverage. I feel API is becoming the negative point for the solution.

I rate Qlik Replicate an eight out of ten for stability.

I rate Qlik Replicate an eight out of ten for scalability.

Qlik Replicate's technical support is really good if you raise your ticket properly and reach out to the right people.

Positive

Qlik Replicate's initial setup is easy.

Installing Qlik Replicate should not take more than two to three days because you deploy, test, and run some scripts.

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 a good product. Qlik Replicate can give complete coverage to a Qlick customer. The solution was previously known as Attunity, and it was a Microsoft and SAP partner for data lake automation. At the time, not many products were available for data lake automation.

Qlik Replicate is a mature and robust solution. While configuring itself, if there are various sources at the start on the left of the screen, Qlik Replicate takes some time to start blending everything.

Overall, I rate Qlik Replicate a seven out of ten.