What do you like best about Qlik Talend Cloud?
We have evaluated Upsolver for replacing an existing batch-based MPP Analytics pipeline.
The main reasons we eventually decided to go with Upsolver for, are:
1. Fast Time-To-Market - implementation time of production-grade solution goes down to a fraction compared to a fully-self-developed solution using either open or closed source tools.
2. Highly efficient \ Cost-Effective
A. The number of developers and IT\devops personnel required to operate the solution is much lower than traditional solutions.
B. real ETL-as-a-service - Upsolver is doing it all for you; it leaves little room for mistake by providing end-to-end coverage of the full application needs - from data loading and scanning, through queuing and up to built-in monitoring capabilities.
C. Compute resources are utilized wisely and precisely to reduce cost as much as possible.
D. you have 0 cost for maintaining the operation
3. Scalable and Flexible:
OOB support for many connectors to either read data from, or output data to.
Smart automatic scaling capabilities by utilizing pre-built scaling strategies.
Upsolver SQL is enriched by all standard and advanced SQL capabilities (json, arrays etc...) and also supports extended capabilities for manipulting special data (eg. geo\ip, URL and more).
4. API and serving:
All Upsolver capabilities are provided in API - this gives many options to automate processes.
Upsolver Lookup is blazing fast when used as key-value store for serving external API needs, with high scale and throughput. This is a big advantage for specific use-cases, and we use it to query our streaming data from our Web API. Review collected by and hosted on G2.com.
What do you dislike about Qlik Talend Cloud?
After using the platform for over 1 year, main drawbacks are:
1. Development cycle is limited; automated deployment cycle is difficult to achieve since Upsolver account is tied to a cloud account where development environments are maintained in a separate model.
2. The tool is aimed for streaming-aggregates data pipeline and lacks the support for more batch-oriented (classic) ETL needs (e.g. controlling the time of a particular output)
3. Incurred license and cloud costs should not be ignored while developing the Upsolver pipeline (as with any cloud-based solution for data processing).
Adding Logic\pipelines and\or compute resources can go "under the radar" quickly, and cost can rise, especially if a developer has no access to the cloud resources console.
* Especially for a project with strict budget borders Review collected by and hosted on G2.com.