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.
Visualizing cross-channel campaign performance can blend data from a few different sources to compare performance metrics like spend, clicks, and conversions side-by-side in a single view, which helps in quick budget reallocation decisions. When dealing with massive volumes of data (millions of rows) or highly complex queries, Looker Studio dashboards can become slow, laggy, or even crash. Performance issues are a frequent complaint when working with large datasets, making it unsuitable for enterprise-level companies
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.
Breath of data - the number of ways to interrogate the data is endless, and the options to view metrics alongside each other make for comprehensive datasets.
Data visualisation and customisation - the options for presenting data and separating out across pages allow for clean visuals and segmented information.
Easy shareability/usability - a quick and simple tool to introduce colleagues to, and easy to grant access for them to be able to view the data, without having to understand the setup itself.
It needs better handling of complex logic. We often need workarounds to perform complex custom calculations, and it can be really unpleasant at times.
Felt it got slow with a larger data set, and in one minor report, we had to set up time filters so that calculations during spikes could be traced more quickly.
Compare to competition they need to improve with notification things.
It is the simplest and least expensive way for us to automate our reporting at this time. I like the ability to customize literally everything about each report, and the ability to send out reports automatically in emails. The only issue we have been having recently is a technical glitch in the automatic email report. Sadly, there is almost no support for this tool from Google, but is also free, so that is important to take into consideration
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.
Looker Studio is easy to use, and it offers a sufficient variety of predefined visualizations to choose from. It's easy for us, and anyone can set up basic reporting without extensive data visualization skills. The interface layout is easy to understand, and it doesn't take long to get used to.
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.
I give it a lower support rating because it seems like our Dev team hasn't gotten the support they need to set up our database to connect. Seems like we hit a roadblock and the project got put on pause for dev. That sucks for me because it is harder to get the dev team to focus on it if they don't get the help they need to set it up.
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.
Looker Studio is far easier to implement, stand up, and learn. The interface is simpler and user-friendly for various levels of data visualization/analysis knowledge and experience. The biggest benefit of Looker Studio, however, is its ease of connection to GA data and speed. Furthermore, since it is an online program/tool, it requires less CPU/battery/storage on the user's device.
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.
