We performed a comparison between Elastic Search and Palantir Foundry based on real PeerSpot user reviews.
Find out in this report how the two Cloud Data Integration solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."The special text processing features in this solution are very important for me."
"The most valuable features are the ease and speed of the setup."
"Search is really powerful."
"The most valuable feature of the solution is its utility and usefulness."
"The AI-based attribute tagging is a valuable feature."
"The forced merge and forced resonate features reduce the data size increasing reliability."
"The solution is quite scalable and this is one of its advantages."
"The solution has great scalability."
"Palantir Foundry is a robust platform that has really strong plugin connectors and provides features for real-time integration."
"Encapsulates all the components without the requirement to integrate or check compatibility."
"The ease of use is my favorite feature. We're able to build different models and projects or combine different projects to build one use case."
"The virtualization tool is useful."
"The AI engine that comes with Palantir Foundry is quite interesting."
"The solution provides an end-to-end integrated tech stack that takes care of all utility/infrastructure topics for you."
"The security is also excellent. It's highly granular, so the admins have a high degree of control, and there are many levels of security. That worked well. You won't have an EDC unless you put everything onto the platform because it is its own isolated thing."
"It's scalable."
"They should improve its documentation. Their official documentation is not very informative. They can also improve their technical support. They don't help you much with the customized stuff. They also need to add more visuals. Currently, they have line charts, bar charts, and things like that, and they can add more types of visuals. They should also improve the alerts. They are not very simple to use and are a bit complex. They could add more options to the alerting system."
"Enterprise scaling of what have been essentially separate, free open source software (FOSS) products has been a challenge, but the folks at Elastic have published new add-ons (X-Pack and ECE) to help large companies grow ELK to required scales."
"Elastic Enterprise Search's tech support is good but it could be improved."
"Its licensing needs to be improved. They don't offer a perpetual license. They want to know how many nodes you will be using, and they ask for an annual subscription. Otherwise, they don't give you permission to use it. Our customers are generally military or police departments or customers without connection to the internet. Therefore, this model is not suitable for us. This subscription-based model is not the best for OEM vendors. Another annoying thing about Elasticsearch is its roadmap. We are developing something, and then they say, "Okay. We have removed that feature in this release," and when we are adapting to that release, they say, "Okay. We have removed that one as well." We don't know what they will remove in the next version. They are not looking for backward compatibility from the customers' perspective. They just remove a feature and say, "Okay. We've removed this one." In terms of new features, it should have an ODBC driver so that you can search and integrate this product with existing BI tools and reporting tools. Currently, you need to go for third parties, such as CData, in order to achieve this. ODBC driver is the most important feature required. Its Community Edition does not have security features. For example, you cannot authenticate with a username and password. It should have security features. They might have put it in the latest release."
"The one area that can use improvement is the automapping of fields."
"It is hard to learn and understand because it is a very big platform. This is the main reason why we still have nothing in production. We have to learn some things before we get there."
"It was not possible to use authentication three years back. You needed to buy the product's services for authentication."
"Elastic Search needs to improve its technical support. It should be customer-friendly and have good support."
"The data lineage was challenging. It's hard to track data from the sources as it moves through stages. Informatica EDC can easily capture and report it because it talks to the metadata. This is generated across those various staging points."
"There is not a wide user base for the solution's online documentation so it is sometimes difficult to find answers."
"The frontend capabilities of Palantir Foundry could be improved."
"The solution's visualization and analysis could be improved."
"It requires a lot of manual work and is very time-consuming to get to a functional point."
"Difficult to receive data from external sources."
"The workflow could be improved."
"The solution could use more online documentation for new users."
Elastic Search is ranked 10th in Cloud Data Integration with 59 reviews while Palantir Foundry is ranked 12th in Cloud Data Integration with 14 reviews. Elastic Search is rated 8.2, while Palantir Foundry is rated 7.6. The top reviewer of Elastic Search writes "Played a crucial role in enhancing our cybersecurity efforts ". On the other hand, the top reviewer of Palantir Foundry writes "The data visualization is fantastic and the security is excellent". Elastic Search is most compared with Faiss, Milvus, Pinecone, Azure Search and Amazon Kendra, whereas Palantir Foundry is most compared with Azure Data Factory, Palantir Gotham, SAP Data Services, AWS Glue and Denodo. See our Elastic Search vs. Palantir Foundry report.
See our list of best Cloud Data Integration vendors.
We monitor all Cloud Data Integration reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.