Qlik Compose Reviews

With Qlik Compose, it depends on what the customer wants to implement because it doesn't perform complex SQL statements without writing code. So in many cases, it's necessary to write the SQL directly to the database. I can say that it's not as simple as stated in the documentation because, in many cases, you have to write SQL code in order to perform some transformations. I say this because Qlik Compose is well known as a that can transform data in order to put them in a data warehouse. So in many cases, it's necessary to pre-transform the source data and then process them in Qlik Compose because the solution is used as a data warehouse automation tool. It is not a tool that performs some SQL modifications. For example, creating a transformation involving more than one table is extremely difficult. In the solution, the recent data quality functionality is a sort of controller of data. So, for example, if you wanted to perform a historical process to take all the modifications in some fields, it does it well.

The fact that in Qlik Compose, you can create the data marks without writing code, and you can connect to several databases as a target only by selecting the data targets and the credentials are some of its features.

Since it lacks in certain areas pertaining to scalability, there is a scope for improving the solution's scalability.

Qlik Compose should consider the fact that there are complex SQL statements without writing codes, documentation is not simple, SQL code is needed in order to make a transformation, and data quality functionality in the solution, and these issues need to be considered for improvement.

I have worked with Qlik Compose for two projects, and based on my experience, I used it to meet the requirements of my customer. So, it was a three-month project. My company has a partnership with Qlik Compose. Also, I am using the solution's latest version.

Stability-wise, I rate the solution a seven out of ten. My issues with the solution's stability are owing to the fact that it has certain bugs causing issues in some functionalities that should be working.

Generally, my customers are enterprise-sized businesses. Scalability-wise, I rate the solution an eight out of ten.

The technical support is very good. I rate the technical support a ten out of ten.

Positive

It's very easy to install. Qlik Compose is not deployed on the cloud since it requires a client-server installation. The time for deployment depends on the needs of the customer. For one customer, we deployed it in three months. And for another customer, it took six months because the customer's needs were more. An architect and, in general, one or two people who are involved in the deployment process.

Regarding the maintenance of the product, during a project, the customer takes care of the maintenance part.

The pricing depends on the discounts that Qlik Compose. On a scale of one to ten, where one is cheap, and ten is very expensive, I rate the solution a six.

I recommend other customers use Qlik Compose. I know that now Qlik Compose is improving a lot of functions and the overall product while implementing a lot of functionalities in the solution. So I think now Qlik Compose is on the correct path for the new implementation of new functionalities. Therefore, I think that no other functionality should be implemented at the moment.

Overall, I rate the solution an eight out of ten.

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.