Qlik Compose Reviews

The primary use cases can change according to the company and requirements. We originally began using it as a data preparation tool, where you could do a data migration afterward. 

To be frank, there is no right answer to this question right now. This is due to the fact that we have not yet deployed this solution to any of our customers yet. This is largely because Qlik has recently come up with an alternative solution. Compose and Qlik Data Catalyst aren't a complete suite. We also haven't gotten any customers to sign onto using it just yet.

Qlik Compose has capabilities to do ETL as well as data integration. If you compare with the Replicate, Replicate can do only data integration it doesn't have ETL capabilities.

The most useful aspect of the solution is that you can have in CDC and ETL. You can also take advantage of storage.

The solution has room for improvement in the ETL. They have an ETL, but when it comes to the monitoring portion, Qlik Compose doesn't provide a feature for monitoring. They should have some monitoring features included in it. In case of any job failures, the solution should be on an auto-fix. 

There should be the ability to trigger the jobs and schedule them. Qlik Compose can't really do that yet. If you talk about a competitor like Informatica, they do have some scheduling platforms available. 

There are basic features in Compose, but not as advanced features for monitoring and scheduling. Monitoring any scheduling features just needs to be in there in the future.

I've been using the solution for almost a year now. The last time I really worked on it was for a POC about 6 months ago.

The solution is stable. When you compare Qlik Compose and Qlik Replicate, if you want to have an integration between the two different sources, it's better to go with Qlik Replicate. However, if you want to have an ETL added into it, then you can go with the Qlik Compose. If you choose that option, you need to be aware that you can't do visualization. If you want to do a complete stack of data integration - with the ETL, as well as visualization - then you need to go with Qlik Data Catalyst. Everything depends upon the business requirements. If I only want the conditioned part, Replicate would be fine. If I required a data integration in terms of only ETL (not visualization), then Compose is better.

As long as you pick the solution that best fits with your requirements, you won't find that performance is a problem. It's good.

The solution can easily handle a lot of data. As soon as you consume the data load, it is easily scalable. 

We currently only have two or three users at our organization that have access to the solution. However, it totally depends on the requirements. If we get the requirement that there would be a lot of users, they need to be trained for deployment and development, etc. As of now, this product is still under exploration within our organization. 

I've never contacted technical support, so I can't speak to the quality of their service at this time.

We previously used a different solution, and Qlik has since taken it over. 

I have experience with Informatica, for example, and Snowflake. I've worked with multiple tools in the past. Qlik is rather new to the market.

The initial setup was not complex. It was quite straightforward.

Deployment is not that hard. You can do it within two hours, or three hours, max. It depends upon how good your knowledge is. For me, it can take even as little as an hour, depending on the setup.

It just takes a few people to deploy it. You don't need a big team. One of my colleagues was a big help. He's a very knowledgeable cloud architect whereas I am an information architect.

I'm a good architect. I have not needed to a consultant. For others, if they needed help or not would depend on certain configurations that may need to get implemented. If you are not from a technical background, then you might require a consultant due to the fact that there are certain parts that need to be stored in configuration files, which need to be done in a proper manner.

I'm not sure of the exact cost structure of the solution. Potential users would have to reach out to the company directly to discuss pricing. My understanding, however, is that you only pay for licensing costs and there are no ancillary fees beyond that.

We are partners with Qlik.

Right now, I have not worked on the system in a hands-on capacity. I have an architectural understanding of the solution. 

Implementing the product is totally dependent upon the business side of an organization. If a company is just mid-scale or smaller in size, Qlik might be perfect. If you have a giant company, then you should aim for bigger products. Qlik Compose only provides for unique capabilities. There are other solutions, like Informatica, which may be better for larger firms with broader needs. 

I would rate the solution six out of ten.

Our company uses Qlik Compose for simple transformations. We use it as a basic ETL solution. 

Qlik Compose is good enough. It is user-friendly and intuitive.

For more complex work, we are not using Qlik Compose because it cannot handle very high volumes at the moment. It needs the same batching capabilities that other ETL tools have. We can't batch the data into small chunks when transforming large amounts of data. It tries to do everything in one shot and that's where it fails.

Qlik also needs the ability to improve more complex combined SQL tables and perform more complicated transformations. I'd like to see better connectivity to some with custom coding languages like Python or Java.

We've been using Qlik Compose for about a year and a half.

Qlik Compose is stable. We haven't had issues except when dealing with high volume. Otherwise, it's okay. 

I don't think Qlik can be used in a high-volume scenario. It didn't work for us.

Support is okay. We don't get the required solutions on time, so I would just say support is average. Yeah.

Setting up Qlik Compose is straightforward. You only need one person to deploy and maintain the solution. 

It was an in-house deployment.

I would Qlik Compose six out of 10. You should understand the product well before using it because it has a learning curve. There are many options, so if you choose the wrong one, you may get stuck with it. If you're trying to do something with high data volumes, this may not be the right choice at the moment.

We use Qlik Compose as a low to no-code data warehouse and data lake generation tool. I use it to build data warehouses and data lakes.

I like modeling and code generation. It has become a pretty handy tool because of its short ideation to delivery time. From the time you decide you are modeling a data warehouse, and once you finish the modeling, it generates all the code, generates all the tables. All you have to do is tick a few things, and you can produce a fully functional warehouse. I also like that they have added all the features I have asked for over four years.

It would be better if the first level of technical support were a bit more technically knowledgeable to solve the problem. I think they could also improve the injection of custom scripts. It is pretty difficult to add additional scripts. If the modeling doesn't give you what you want, and you want to change the script generated by the modeling, it is a bit more challenging than in most other products. It is very good with standard form type systems, but if you get a more complicated data paradigm, it tends to struggle with transforming that into a model.

I have been involved with Qlik Compose for about six years.

Qlik Compose is a stable solution.

On a scale from one to ten, I would give stability an eight.

Qlik Compose is a scalaible solution. If you are in the cloud, scaling is straightforward. If you are on-premises, you are scaling by adding either RAM or space, which can be a bit more challenging. If you look at their documentation, it has a relatively straightforward grid-type thing.

On a scale from one to ten, I would give scalability a seven.

Their first level of support could do with some improvement. If I log a call or submit a problem, I tend to find that I have to repeat myself because the person who first gets it is the first level of support. They do the same kind of thing, and they have a script. They ask questions like "have you rebooted? Have you checked this, or have you done that?"

On a scale from one to ten, I would give technical support an eight.

Positive

The initial setup is straightforward. It takes about 20 minutes to deploy this solution.

On a scale from one to ten, I would give the initial setup a nine.

On a scale from one to ten, I would give Qlik Compose an eight.

Our primary use case would be in small projects or in some very straightforward data integration processes, such as the one-to-one replication of databases without complex transformation needs.

I have found it to be a very good, stable, and strong product.

When you replicate data, you need to transform the data into formats that are easier for querying and reporting, or data warehousing. I think the set of transformation functions can be improved. In large organizations, in particular, there are many dependencies between different paths. So to easily manage the ETL environment, you need to have visual data flow management capabilities. I believe that visual data flow management should be improved.

I used this solution in a couple of projects in the last 15 years.

My impression is that the product is very stable.

I have found customer service/technical support to be good.

I think it would be very straightforward to setup as shown in our test environment.