We performed a comparison between Elastic Search and Loom Systems based on real PeerSpot user reviews.
Find out in this report how the two Indexing and Search solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."The most valuable features are the ease and speed of the setup."
"It gives us the possibility to store and query this data and also do this efficiently and securely and without delays."
"The most valuable features are the data store and the X-pack extension."
"The most valuable feature of the solution is its utility and usefulness."
"The solution is quite scalable and this is one of its advantages."
"The tool's stability and performance are good."
"The initial setup is very easy for small environments."
"We can easily collect all the data and view historical trends using the product. We can view the applications and identify the issues effectively."
"What I like best about Loom Systems is that you can use it for infrastructure monitoring. I also like that it's a flexible solution."
"The solution is absolutely scalable. If an organization needs to expand it out they definitely can."
"You can develop your own apps within Loom, and they can be configured very simply."
"The RFS portion of the solution is the product's most valuable feature."
"There are challenges with performance management and scalability."
"Elastic Enterprise Search could improve the report templates."
"There is another solution I'm testing which has a 500 record limit when you do a search on Elastic Enterprise Search. That's the only area in which I'm not sure whether it's a limitation on our end in terms of knowledge or a technical limitation from Elastic Enterprise Search. There is another solution we are looking at that rides on Elastic Enterprise Search. And the limit is for any sort of records that you're doing or data analysis you're trying to do, you can only extract 500 records at a time. I know the open-source nature has a lot of limitations, Otherwise, Elastic Enterprise Search is a fantastic solution and I'd recommend it to anyone."
"The documentation regarding customization could be better."
"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."
"It should be easier to use. It has been getting better because many functions are pre-defined, but it still needs improvement."
"They could improve some of the platform's infrastructure management capabilities."
"Better dashboards or a better configuration system would be very good."
"The discovery and mapping still takes a lot of human intervention, it's quite resource heavy,"
"The reporting is a bit weak. They should work to improve this aspect of the product."
"The change management within the solution needs to be improved. There needs to be more process automation."
"What's lacking in Loom Systems is the level of priority for each incident. For example, after implementation and there was a huge impact on the client, and the client comes back to you and says that there's an incident, that there needs to be an immediate resolution for it, you'll see severity one, severity two, etc., in Loom Systems, rather than priority levels. It would be better if the incidents can be defined as low priority, medium priority, or high priority."
Elastic Search is ranked 1st in Indexing and Search with 59 reviews while Loom Systems is ranked 57th in IT Infrastructure Monitoring with 4 reviews. Elastic Search is rated 8.2, while Loom Systems is rated 8.0. The top reviewer of Elastic Search writes "Played a crucial role in enhancing our cybersecurity efforts ". On the other hand, the top reviewer of Loom Systems writes "Simple and very effective for developing and configuring apps with great integration capabilities". Elastic Search is most compared with Faiss, Milvus, Pinecone, Azure Search and Amazon Kendra, whereas Loom Systems is most compared with VMware Aria Operations for Applications and Splunk Infrastructure Monitoring. See our Elastic Search vs. Loom Systems report.
We monitor all Indexing and Search 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.