Elasticsearch vs. Tableau Cloud

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.

Incentivized

If you're using Tableau as the primary BI tool, then Tableau Cloud is well suited to publish and share the results with a wide(r) audience. It is well suited for various degrees of self-service proficiency, from pure consumers of analytical work to more advanced users who can use web editing for smaller or larger adjustments, and even for desktop power users who will publish their work to Tableau Cloud. It has many good ways to organize the content and make it easily accessible via search, favorites, folders, collections ("playlists for your data"), or history ("recents"). It might not be ideally suited if there are many on-prem sources to be used (even though there are options to connect them) or if you have very special requirements regarding custom server setup, which is limited in a shared cloud environment like Tableau Cloud.

Incentivized

• 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.

Incentivized

• Tableau Online is completely cloud based and that's why the reports and dashboards are accessible even on the go. One doesn't always need to access the office laptop to access the reports.
• The visualizations are interactive and one can quickly change the level at which they want to view the information. For example, one person might be more interested in looking at the country level performances rather than client level. This is intuitive and one doesn't need to create multiple reports for the same.
• The feature to ask questions in plain vanilla English language is great and helpful. For quick adhoc fact checks one can simply type what they are looking for and the Natural Language Programming algorithms under the hood parse the query, interpret it and then fetch the results accordingly in a visual form.

Incentivized

• 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

Incentivized

• Can be a steep learning curve for new users
• Modeling and building algorithms aren't always intuitive and take some testing/retesting to ensure it's working as it should
• Inability to integrate easily with our HRIS platform. Reports are pulled from HRIS at various intervals and uploaded into Tableau

Incentivized

We're pretty heavily invested in ElasticSearch at this point, and there aren't any obvious negatives that would make us reconsider this decision.

Incentivized

The tool's capacity to handle complex data sources.

Incentivized

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.

Incentivized

Based on comments from our clients, I awarded it this grade. Non-technical customers frequently compliment us on the ease with which they can utilize Tableau Online. Usability is rarely a source of contention amongst our customers. Few complaints have come from me as a user of our internal products.

Incentivized

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.

Incentivized

I have not had any issues that require customer support from Tableau at this time, which speaks well to Tableau. I have taken an online course with Tableau and it was very professional and well done, so based on that I would assume a similar level of quality for their customer service.

Incentivized

Do not mix data and master roles. Dedicate at least 3 nodes just for Master

Incentivized

I wasn't part of the implementation team

Incentivized

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.

Incentivized

In determining whether to go with Tableau Online versus Alteryx, two important factors stood out in determining our go-to solution. First, while Alteryx is an impressive tool for data cleansing, it did not stack up in terms of data visualization capabilities. Tableau, on the other hand, provided us everything we needed in terms of visualizing our data and analytics. The second factor is cost. Well neither solution would be considered cheap, Tableau was the more cost effective solution for our needs.

Incentivized

• 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.

Incentivized

• When we release new products, we are now able to quickly see data and toggle between current periods and previous to see performance
• Generating new reports requires less IT time to build
• Data can be shared across many different device types
• We now have integration where our customers can extract data from our software more easily-this was a big ask from our customers

Incentivized