What users are saying about
151 Ratings
195 Ratings
151 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow noopener'>trScore algorithm: Learn more.</a>
Score 8.7 out of 100
195 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow noopener'>trScore algorithm: Learn more.</a>
Score 8.3 out of 100

Attribute Ratings

  • Apache Spark is rated higher in 2 areas: Likelihood to Recommend, Support Rating
  • Elasticsearch is rated higher in 1 area: Usability
  • Apache Spark and Elasticsearch are tied in 1 area: Likelihood to Renew

Likelihood to Recommend

9.4

Apache Spark

94%
23 Ratings
9.1

Elasticsearch

91%
46 Ratings

Likelihood to Renew

10.0

Apache Spark

100%
1 Rating
10.0

Elasticsearch

100%
1 Rating

Usability

9.4

Apache Spark

94%
2 Ratings
10.0

Elasticsearch

100%
1 Rating

Support Rating

8.6

Apache Spark

86%
6 Ratings
7.8

Elasticsearch

78%
18 Ratings

Implementation Rating

Apache Spark

N/A
0 Ratings
9.0

Elasticsearch

90%
2 Ratings

Likelihood to Recommend

Apache

The software appears to run more efficiently than other big data tools, such as Hadoop. Given that, Apache Spark is well-suited for querying and trying to make sense of very, very large data sets. The software offers many advanced machine learning and econometrics tools, although these tools are used only partially because very large data sets require too much time when the data sets get too large. The software is not well-suited for projects that are not big data in size. The graphics and analytical output are subpar compared to other tools.
Read full review

Elastic

Elasticsearch is a really scalable solution that can fit a lot of needs, but the bigger and/or those needs become, the more understanding & infrastructure you will need for your instance to be running correctly. Elasticsearch is not problem-free - you can get yourself in a lot of trouble if you are not following good practices and/or if are not managing the cluster correctly. Licensing is a big decision point here as Elasticsearch is a middleware component - be sure to read the licensing agreement of the version you want to try before you commit to it. Same goes for long-term support - be sure to keep yourself in the know for this aspect you may end up stuck with an unpatched version for years.
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

Elastic

  • As I mentioned before, Elasticsearch's flexible data model is unparalleled. You can nest fields as deeply as you want, have as many fields as you want, but whatever you want in those fields (as long as it stays the same type), and all of it will be searchable and you don't need to even declare a schema beforehand!
  • Elastic, the company behind Elasticsearch, is super strong financially and they have a great team of devs and product managers working on Elasticsearch. When I first started using ES 3 years ago, I was 90% impressed and knew it would be a good fit. 3 years later, I am 200% impressed and blown away by how far it has come and gotten even better. If there are features that are missing or you don't think it's fast enough right now, I bet it'll be suitable next year because the team behind it is so dang fast!
  • Elasticsearch is really, really stable. It takes a lot to bring down a cluster. It's self-balancing algorithms, leader-election system, self-healing properties are state of the art. We've never seen network failures or hard-drive corruption or CPU bugs bring down an ES cluster.
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

Elastic

  • Joining data requires duplicate de-normalized documents that make parent child relationships. It is hard and requires a lot of synchronizations
  • Tracking errors in the data in the logs can be hard, and sometimes recurring errors blow up the error logs
  • Schema changes require complete reindexing of an index
Read full review

Pricing Details

Apache Spark

Starting Price

Editions & Modules

Apache Spark editions and modules pricing
EditionModules

Footnotes

    Offerings

    Free Trial
    Free/Freemium Version
    Premium Consulting/Integration Services

    Entry-level set up fee?

    No setup fee

    Additional Details

    Elasticsearch

    Starting Price

    $0

    Editions & Modules

    Elasticsearch editions and modules pricing
    EditionModules
    Standard$16.001
    Gold$19.002
    Platinum$22.003
    EnterpriseContact Sales4

    Offerings

    Free Trial
    Free/Freemium Version
    Premium Consulting/Integration Services

    Entry-level set up fee?

    No setup fee

    Additional Details

    Likelihood to Renew

    Apache

    Capacity of computing data in cluster and fast speed.
    Read full review

    Elastic

    We're pretty heavily invested in ElasticSearch at this point, and there aren't any obvious negatives that would make us reconsider this decision.
    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

    Elastic

    To get started with Elasticsearch, you don't have to get very involved in configuring what really is an incredibly complex system under the hood. You simply install the package, run the service, and you're immediately able to begin using it. You don't need to learn any sort of query language to add data to Elasticsearch or perform some basic searching. If you're used to any sort of RESTful API, getting started with Elasticsearch is a breeze. If you've never interacted with a RESTful API directly, the journey may be a little more bumpy. Overall, though, it's incredibly simple to use for what it's doing under the covers.
    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

    Elastic

    We've only used it as an opensource tooling. We did not purchase any additional support to roll out the elasticsearch software. When rolling out the application on our platform we've used the documentation which was available online. During our test phases we did not experience any bugs or issues so we did not rely on support at all.
    Read full review

    Implementation Rating

    Apache

    No answers on this topic

    Elastic

    Do not mix data and master roles. Dedicate at least 3 nodes just for Master
    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

    Elastic

    As far as we are concerned, Elasticsearch is the gold standard and we have barely evaluated any alternatives. You could consider it an alternative to a relational or NoSQL database, so in cases where those suffice, you don't need Elasticsearch. But if you want powerful text-based search capabilities across large data sets, Elasticsearch is the way to go.
    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

    Elastic

    • We have had great luck with implementing Elasticsearch for our search and analytics use cases.
    • While the operational burden is not minimal, operating a cluster of servers, using a custom query language, writing Elasticsearch-specific bulk insert code, the performance and the relative operational ease of Elasticsearch are unparalleled.
    • We've easily saved hundreds of thousands of dollars implementing Elasticsearch vs. RDBMS vs. other no-SQL solutions for our specific set of problems.
    Read full review

    Add comparison