What is our primary use case?
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.
What is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
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.
What do I think about the stability of the solution?
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.
What do I think about the scalability of the solution?
Generally, my customers are enterprise-sized businesses. Scalability-wise, I rate the solution an eight out of ten.
How are customer service and support?
The technical support is very good. I rate the technical support a ten out of ten.
How would you rate customer service and support?
How was the initial setup?
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.
What's my experience with pricing, setup cost, and licensing?
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.
What other advice do I have?
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.
*Disclosure: My company has a business relationship with this vendor other than being a customer. Partner
