No more typing reviews! Try our Samantha, our new voice AI agent.

AtScale Adaptive Analytics (A3) vs Spark SQL comparison

Why PeerSpot?

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

AtScale Adaptive Analytics ...
Average Rating
5.0
Number of Reviews
1
Ranking in other categories
Data Virtualization (7th), BI (Business Intelligence) Tools (44th), Data Governance (41st), BI on Hadoop (1st)
Spark SQL
Average Rating
7.8
Reviews Sentiment
7.6
Number of Reviews
15
Ranking in other categories
Hadoop (4th)
 

Mindshare comparison

AtScale Adaptive Analytics (A3) and Spark SQL aren’t in the same category and serve different purposes. AtScale Adaptive Analytics (A3) is designed for Data Virtualization and holds a mindshare of 7.1%, up 5.9% compared to last year.
Spark SQL, on the other hand, focuses on Hadoop, holds 5.3% mindshare, down 7.9% since last year.
Data Virtualization Mindshare Distribution
ProductMindshare (%)
AtScale Adaptive Analytics (A3)7.1%
Denodo24.5%
SAP HANA18.3%
Other50.099999999999994%
Data Virtualization
Hadoop Mindshare Distribution
ProductMindshare (%)
Spark SQL5.3%
Cloudera Distribution for Hadoop14.6%
Apache Spark14.4%
Other65.7%
Hadoop
 

Featured Reviews

it_user822762 - PeerSpot reviewer
Senior BI and Reporting Analyst at a financial services firm with 10,001+ employees
The GUI interface is nice and easy to use, but the organization of the icons is not saved across users
Connecting to a Hadoop database to create a cube to connect to Tableau. We want to be able to easily create cubes which can be connected to Tableau for visualization The product had many issues. We had great collaboration with the product development team, but the product was not able to meet our…
Kemal Duman - PeerSpot reviewer
Team Lead, Data Engineering at Nesine.com
Data pipelines have run faster and support flexible batch and streaming transformations
We do not have any performance problems, but we do have some resource problems. Spark SQL consumes so many resources that we migrated our streaming job from Spark to Apache Flink. Resource management in Spark SQL should be better. It consumes more resources, which is normal. The main reason we switched from Spark is memory and CPU consumption. The major reason is the resource problem because the number of streaming jobs has been increasing in our company. That is why we considered resource management as a priority. Because of the resource consumption, I would say the development of Spark SQL is better. For development purposes, it is a top product and not difficult to work with, but resources are the major problem. We changed to Flink regardless of development time. Development time is less in Spark compared with Flink.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"The GUI interface is nice and easy to use."
"Data validation and ease of use are the most valuable features."
"Speed is the major benefit of using Spark SQL."
"One of Spark SQL's most beautiful features is running parallel queries to go through enormous data."
"The team members don't have to learn a new language and can implement complex tasks very easily using only SQL."
"Spark SQL's efficiency in managing distributed data and its simplicity in expressing complex operations make it an essential part of our data pipeline."
"The solution is easy to understand if you have basic knowledge of SQL commands."
"Overall the solution is excellent."
"I find the Thrift connection valuable."
 

Cons

"The product was not able to meet our 10 second refresh requirements."
"The organization of the icons is not saved across users."
"There was an issue with the incremental aggregation not working as indicated."
"I've experienced some incompatibilities when using the Delta Lake format."
"Spark SQL consumes so many resources that we migrated our streaming job from Spark to Apache Flink."
"The solution needs to include graphing capabilities. Including financial charts would help improve everything overall."
"In the next release, maybe the visualization of some command-line features could be added."
"Being a new user, I am not able to find out how to partition it correctly."
"In the next update, we'd like to see better performance for small points of data. It is possible but there are better tools that are faster and cheaper."
"There are many inconsistencies in syntax for the different querying tasks like selecting columns and joining between two tables so I'd like to see a more consistent syntax."
"Anything to improve the GUI would be helpful."
 

Pricing and Cost Advice

Information not available
"We use the open-source version, so we do not have direct support from Apache."
"The solution is open-sourced and free."
"We don't have to pay for licenses with this solution because we are working in a small market, and we rely on open-source because the budgets of projects are very small."
"There is no license or subscription for this solution."
"The on-premise solution is quite expensive in terms of hardware, setting up the cluster, memory, hardware and resources. It depends on the use case, but in our case with a shared cluster which is quite large, it is quite expensive."
"The solution is bundled with Palantir Foundry at no extra charge."
report
Use our free recommendation engine to learn which Data Virtualization solutions are best for your needs.
920,574 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Comms Service Provider
15%
Healthcare Company
13%
Manufacturing Company
11%
Construction Company
10%
Financial Services Firm
15%
Comms Service Provider
11%
Manufacturing Company
11%
University
9%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
By reviewers
Company SizeCount
Small Business5
Midsize Enterprise6
Large Enterprise4
 

Questions from the Community

Ask a question
Earn 20 points
What needs improvement with Spark SQL?
We do not have any performance problems, but we do have some resource problems. Spark SQL consumes so many resources that we migrated our streaming job from Spark to Apache Flink. Resource manageme...
What is your primary use case for Spark SQL?
Spark SQL has been in our stack for less than one year, though some of our colleagues are using it. It is a useful product for transformation jobs. We generally use Spark SQL for batch processing. ...
What advice do you have for others considering Spark SQL?
Regarding the Catalyst query optimizer, I think we are using it. We were using it in the past, but I am not certain if we use it now. We used it a long time ago. I rate my experience with Spark SQL...
 

Also Known As

AtScale, AtScale Intelligence Platform
No data available
 

Overview

 

Sample Customers

Rakuten, TD Bank, Aetna, Glaxo-Smith Kline, Biogen, Toyota, Tyson
UC Berkeley AMPLab, Amazon, Alibaba Taobao, Kenshoo, Hitachi Solutions