Qlik Compose Reviews

It is primarily a data integration tool for us. When it comes to the Qlik data integration aspect, it was extremely complete and one of the best platforms I've seen.

I work with a company that is focused on data integration, and Qlik was the preferred tool.

There were many valuable features, such as extracting any data to put in the cloud. For example, Qlik was able to gather data from SAP and extract SAP data from the platforms. They could create a data hub for clients with all the protection and features needed. 

Some of the other features include data warehouse automation, CDC's training, managed Data Lake Creation, and Guardant Data catalogs, which were very useful in analytics applications. It's not the most complete tool for data integration, but it is still impressive.

Currently, Qlik's ETL and data transformation could be better. Also, the implementation can be improved because it is complicated. At first, it's really difficult for partners and clients to understand the platform and to work with it. The integration is very siloed within the IT department and IT architecture teams, which causes friction when trying to distribute it to businesses.

Additionally, they don't have the most user-friendly platform for visualizing data. Qlik was initially a data visualization tool, but it became a full data pipeline company after acquiring many companies. However, even after three or four years, they still have some challenges with data integration implementation within the clients.

Moreover, their support team could also be better. The support is also not very good.

Qlik Compose is a legacy product opportunity that is more focused on the data integration side. Qlik has a whole pipeline that goes from data integration to data literacy. So, I have some experience with Qlik Compose.

Qlik should have more people working for support and be faster, especially for large clients. The SLA is 24 hours for large clients, which is ridiculous whenever you have companies that can solely chew. Oftentimes, they do not respond within 24 hours, so there is an issue with internal communication when we have an issue with support. There is a lot of room for improvement in Qlik's support team.

Neutral

Overall, I would rate Qlik compose an eight out of ten. It is a good platform. 

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

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.