Overview
ProductRatingMost Used ByProduct SummaryStarting Price
Apache Spark
Score 8.8 out of 10
N/A
N/AN/A
SingleStore
Score 8.4 out of 10
N/A
SingleStore aims to enable organizations to scale from one to one million customers, handling SQL, JSON, full text and vector workloads in one unified platform.
$0.69
per hour
Pricing
Apache SparkSingleStore
Editions & Modules
No answers on this topic
OnDemand
$0.69
per hour
Offerings
Pricing Offerings
Apache SparkSingleStore
Free Trial
NoYes
Free/Freemium Version
NoYes
Premium Consulting/Integration Services
NoYes
Entry-level Setup FeeNo setup feeOptional
Additional Details
More Pricing Information
Community Pulse
Apache SparkSingleStore
Considered Both Products
Apache Spark

No answer on this topic

SingleStore
Chose SingleStore
The in-memory tech is the best in class. If perf. is the hard limit then this is the No.1 to go.
When data scales up, the cost of maintaining a big cluster with memory keep increasing (both the infrastructure cost and licensing cost) becomes high. Also the balance between …
Chose SingleStore
I have tried using CSV as a back-end storage, yet I/O is very heavy, direct transit from spark to SingleStore DB (formerly MemSQL) in memory really beats.
Top Pros
Top Cons
Best Alternatives
Apache SparkSingleStore
Small Businesses

No answers on this topic

Google Cloud SQL
Google Cloud SQL
Score 8.8 out of 10
Medium-sized Companies
Cloudera Manager
Cloudera Manager
Score 9.9 out of 10
Snowflake
Snowflake
Score 8.9 out of 10
Enterprises
IBM Analytics Engine
IBM Analytics Engine
Score 7.9 out of 10
SAP IQ
SAP IQ
Score 9.0 out of 10
All AlternativesView all alternativesView all alternatives
User Ratings
Apache SparkSingleStore
Likelihood to Recommend
10.0
(23 ratings)
8.7
(57 ratings)
Likelihood to Renew
10.0
(1 ratings)
9.1
(4 ratings)
Usability
10.0
(3 ratings)
9.1
(7 ratings)
Availability
-
(0 ratings)
9.1
(1 ratings)
Performance
-
(0 ratings)
9.3
(31 ratings)
Support Rating
8.7
(4 ratings)
9.1
(7 ratings)
Implementation Rating
-
(0 ratings)
9.1
(1 ratings)
Ease of integration
-
(0 ratings)
9.1
(1 ratings)
Product Scalability
-
(0 ratings)
9.1
(1 ratings)
Vendor post-sale
-
(0 ratings)
9.1
(1 ratings)
Vendor pre-sale
-
(0 ratings)
9.1
(1 ratings)
User Testimonials
Apache SparkSingleStore
Likelihood to Recommend
Apache
Well suited: To most of the local run of datasets and non-prod systems - scalability is not a problem at all. Including data from multiple types of data sources is an added advantage. MLlib is a decently nice built-in library that can be used for most of the ML tasks. Less appropriate: We had to work on a RecSys where the music dataset that we used was around 300+Gb in size. We faced memory-based issues. Few times we also got memory errors. Also the MLlib library does not have support for advanced analytics and deep-learning frameworks support. Understanding the internals of the working of Apache Spark for beginners is highly not possible.
Read full review
SingleStore
SingleStore HTAP engine is well suited for real-time analytics, fast ingestion, scaling OLTP system like MySQL. When you need to run reports or perform aggregates on billions of rows and you get result in seconds, you cannot get this experience with other OLTP engines. I wish DBtLab was a little more developer and supported for SingleStore. This would allow to perform better data transformation. You can use stored procedures, but DBTLabs has become a standard for dimensional modeling in data warehousing projects. This is probably why SingleStore has trouble piercing in the data warehouse world. It is definately capable to compete with Snowflake when it comes to scalability, query performance, data compression, but Snowflake has ravaged the data warehouse market in few years and large corporations have already invested lots of money in migrating into Snowflake. The SingleStore community needs to grow. Everyone who uses SingleStore loves it.
Read full review
Pros
Apache
  • Rich APIs for data transformation making for very each to transform and prepare data in a distributed environment without worrying about memory issues
  • Faster in execution times compare to Hadoop and PIG Latin
  • Easy SQL interface to the same data set for people who are comfortable to explore data in a declarative manner
  • Interoperability between SQL and Scala / Python style of munging data
Read full review
SingleStore
  • Technical support is stellar -- far above and beyond anything I've experienced with any other company.
  • When we compared SingleStore to other databases two years ago, we found SingleStore performance to be far superior.
  • Pipeline data ingestion is exceptionally fast.
  • The ability to combine transactional and analytical workloads without compromising performance is very impressive.
Read full review
Cons
Apache
  • Memory management. Very weak on that.
  • PySpark not as robust as scala with spark.
  • spark master HA is needed. Not as HA as it should be.
  • Locality should not be a necessity, but does help improvement. But would prefer no locality
Read full review
SingleStore
  • We wish the product had better support for High Availability of the aggregator. Currently the indexes generated by the two different aggregators are not in the same sequential space and so our apps have more burden to deal with HA.
  • More tools for debugging issues such as high memory usage would be good.
  • The price was the one that kept us away from purchasing for the first few years. Now we are able to afford due to a promotion that gives it at 25% of the list price. Not sure if we'll continue after the promotion offer expires in another 2 years.
Read full review
Likelihood to Renew
Apache
Capacity of computing data in cluster and fast speed.
Read full review
SingleStore
We haven't seen a faster relation database. Period. Which is why we are super happy customers and will for sure renew our license.
Read full review
Usability
Apache
The only thing I dislike about spark's usability is the learning curve, there are many actions and transformations, however, its wide-range of uses for ETL processing, facility to integrate and it's multi-language support make this library a powerhouse for your data science solutions. It has especially aided us with its lightning-fast processing times.
Read full review
SingleStore
[Until it is] supported on AWS ECS containers, I will reserve a higher rating for SingleStore. Right now it works well on EC2 and serves our current purpose, [but] would look forward to seeing SingleStore respond to our urge of feature in a shorter time period with high quality and security.
Read full review
Reliability and Availability
Apache
No answers on this topic
SingleStore
We have not experienced any downtime in the two years that we have been using SingleStore.
Read full review
Performance
Apache
No answers on this topic
SingleStore
SingleStore's performance is incredible. Our predictive algorithms went from taking 24-48 HOURS down to 15 minutes allowing our team to run those much more frequently. Previously, we were limited to about 60 requests per minute due to table locks. Implementing columnstore on SingleStore allowed us to receive 1000 requests per minute.
Read full review
Support Rating
Apache
1. It integrates very well with scala or python. 2. It's very easy to understand SQL interoperability. 3. Apache is way faster than the other competitive technologies. 4. The support from the Apache community is very huge for Spark. 5. Execution times are faster as compared to others. 6. There are a large number of forums available for Apache Spark. 7. The code availability for Apache Spark is simpler and easy to gain access to. 8. Many organizations use Apache Spark, so many solutions are available for existing applications.
Read full review
SingleStore
Very responsive to trouble tickets - Often, I think, the SingleStore's monitoring systems have already alerted the engineers by the time I get around to writing a ticket (about 10 - 20 mins after we see a problem). I feel like things are escalated nicely and SingleStore takes resolving trouble tickets seriously. Also SingleStore follows up after incidents to with a post mortem and actionable takaways to improve the product. Very satisfied here.
Read full review
Implementation Rating
Apache
No answers on this topic
SingleStore
We allowed 2-3 months for a thorough evaluation. We saw pretty quickly that we were likely to pick SingleStore, so we ported some of our stored procedures to SingleStore in order to take a deeper look. Two SingleStore people worked closely with us to ensure that we did not have any blocking problems. It all went remarkably smoothly.
Read full review
Alternatives Considered
Apache
Spark in comparison to similar technologies ends up being a one stop shop. You can achieve so much with this one framework instead of having to stitch and weave multiple technologies from the Hadoop stack, all while getting incredibility performance, minimal boilerplate, and getting the ability to write your application in the language of your choosing.
Read full review
SingleStore
Timescale was the biggest alternative option we looked at for SingleStore, however the requirement to learn a new syntax (due to not being SQL compatible) was our biggest pain point. Supporting a new language would require alterations to the Laravel framework, as this only offered SQL integration out of the box. This alteration would be time consuming and would limit our scope to future hiring due to the new syntax.
Read full review
Scalability
Apache
No answers on this topic
SingleStore
We needed more memory on our cluster. SingleStore handled it very smoothly.
Read full review
Return on Investment
Apache
  • Business leaders are able to take data driven decisions
  • Business users are able access to data in near real time now . Before using spark, they had to wait for at least 24 hours for data to be available
  • Business is able come up with new product ideas
Read full review
SingleStore
  • As the overall performance and functionality were expanded, we are able to deliver our data much faster than before, which increases the demand for data.
  • Metadata is available in the platform by default, like metadata on the pipelines. Also, the information schema has lots of metadata, making it easy to load our assets to the data catalog.
Read full review
ScreenShots