No more typing reviews! Try our Samantha, our new voice AI agent.

Elastic Search vs IBM InfoSphere Information Server comparison

Why PeerSpot?
 

Comparison Buyer's Guide

Executive Summary

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

Elastic Search
Average Rating
8.2
Reviews Sentiment
6.5
Number of Reviews
100
Ranking in other categories
Indexing and Search (1st), Cloud Data Integration (6th), Search as a Service (1st), Vector Databases (6th)
IBM InfoSphere Information ...
Average Rating
8.2
Reviews Sentiment
5.8
Number of Reviews
9
Ranking in other categories
Data Integration (33rd), Metadata Management (8th)
 

Featured Reviews

reviewer2817942 - PeerSpot reviewer
Senior Software Engineer at a consultancy with 11-50 employees
Logging and vector search have transformed observability and empowered reliable ai agents
Elastic Search is not specifically being used for certain purposes. I deploy Elastic Search database on the cloud and use cloud services so that nobody can attack. However, I do not use Elastic Search to resolve attack issues. The basic main purpose of Elastic Search, as of now, I feel it can do more in the AI area. Sometime I saw that when I am developing RAG and have to generate the embeddings, which I call metadata, sometimes it tries to fail. That durability or issue handling should be improved, but apart from that, I did not find anything as of now. As per my use case, whatever I am using seems pretty good. Apart from that, some definitely improvement will be there. One improvement is that it should be faster. Whenever I am searching any logs, it takes much time. For example, if I open my log in Notepad or a similar tool, I can search the text within a second. With Elastic Search, it takes a little bit of time, ten to fifteen seconds. That can be improved. Sometimes, engineers take time to assign when I create a ticket.
MI
Senior Data Engineer at Mohammed Mansour Alrumiah
Faced challenges with customer support and documentation but have benefited from reliable data integration over the years
As for utilizing the platform's metadata management feature, I have not worked on that feature yet, but personally, I have done that. To evaluate the effectiveness of IBM InfoSphere Information Server's data integration capabilities, if IBM is providing all the solutions we are using, then it is definitely a helpful thing. Mostly, the other thing is that it is a big area including data governance, data lineage, data management, and metadata, but every customer is not putting that much effort and money on that. They mostly migrate the data, use it, and forget it, but slowly things are changing. I am working in Saudi Arabia, so here also data governance, data management, and those kinds of things are getting attention. Regarding how scalable IBM InfoSphere Information Server is, I need to learn how to tune performance and scalability on the cloud. I am familiar with localized hardware, but on the cloud, I still have to do the work around it. In the beginning, we estimate the load and based on that, we put the hardware, but if there is continuous increase, I believe IBM also faces problems. Scalability needs to be improved because once the demand comes, you should be able to improve it, but for that, documentation on how to add hardware or resources to the software needs to be proper. I do not have much hands-on experience with that.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"Aggregation is faster than querying directly from a database, like Postgres or Vertica, and it's much faster if I want to do aggregation, which allows me to store logs and find anomalies effectively."
"I think that Elasticsearch is a good product and cheaper than Splunk."
"The most valuable feature for us is the analytics that we can configure and view using Kibana."
"The ability to aggregate log and machine data into a searchable index reduces time to identify and isolate issues for an application. Saves time in triage and incident response by eliminating manual steps to access and parse logs on separate systems, within large infrastructure footprints."
"The AI-based attribute tagging is a valuable feature."
"We can easily collect all the data and view historical trends using the product. We can view the applications and identify the issues effectively."
"You have dashboards, it is visual, there are maps, you can create canvases. It's more visual than anything that I've ever used."
"The solution is quite scalable and this is one of its advantages."
"Over the years of working with IBM InfoSphere Information Server, I see basically the strength of the tool, capability, and load balancing, which I see is really good."
"Deploying the solution is straightforward for me."
"The initial IBM InfoSphere Information Server is straightforward and you can choose what type of installation you want, such as a customized installation, with clear-cut documentation that, if followed, works fine and the installation has not given us issues."
"Data connections, data partitioning, flexibility, and performance are the most valuable features."
"This solution has reduced the time it takes for ETL. We took an existing Teradata ETL application from three days to eight minutes."
"Reduces the loading and development time for Datawarehouse ETL."
"The integration with different technologies is the most valuable feature."
"IBM InfoSphere Information Server is stable."
 

Cons

"The setup is somewhat complicated due to multiple dependencies and relations with different systems."
"It was not possible to use authentication three years back. You needed to buy the product's services for authentication."
"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 metadata gets stored along with indexes and isn't queryable."
"New Relic could be more flexible, similar to Elasticsearch."
"We had initially planned to expand use of ELK because of its cheap price and the services that are included, but given the difficulty with implementation we've decided to go with Nagios instead."
"What they need is to be more transparent about the actual setup of the cluster and the deployment process."
"I would rate technical support from Elastic Search as three out of ten. The main issue is a general sum of all factors."
"Customer Service: It's poor."
"This solution would benefit from the engine being made more lightweight."
"We have decided to decrease the usage of metadata management because we did not see any significant advantages."
"Heavy use of scratch disk which sometimes leads to failure."
"IBM InfoSphere Information Server should be more scalable. It should have the option to change the configuration to run on a single, non-multiple node, or multi-threading processing."
"Unlike other tools, IBM tools do not provide much help from the internet, so additional support should be available."
"Their technical support needs improvement."
"There are certain shortcomings in the cloud side of the solution, where improvements are required."
 

Pricing and Cost Advice

"The version of Elastic Enterprise Search I am using is open source which is free. The pricing model should improve for the enterprise version because it is very expensive."
"It can be expensive."
"The price could be better."
"This is a free, open source software (FOSS) tool, which means no cost on the front-end. There are no free lunches in this world though. Technical skill to implement and support are costly on the back-end with ELK, whether you train/hire internally or go for premium services from Elastic."
"We are paying $1,500 a month to use the solution. If you want to have endpoint protection you need to pay more."
"The pricing model is questionable and needs to be addressed because when you would like to have the security they charge per machine."
"We are using the free open-sourced version of this solution."
"Although the ELK Elasticsearch software is open-source, we buy the hardware."
"The licensing cost of IBM InfoSphere Information Server depends on how many users there are."
report
Use our free recommendation engine to learn which Cloud Data Integration solutions are best for your needs.
915,341 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
11%
Manufacturing Company
9%
Outsourcing Company
9%
Comms Service Provider
7%
Financial Services Firm
15%
Construction Company
14%
Comms Service Provider
9%
Manufacturing Company
9%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business40
Midsize Enterprise12
Large Enterprise50
By reviewers
Company SizeCount
Small Business5
Midsize Enterprise1
Large Enterprise5
 

Questions from the Community

What is your experience regarding pricing and costs for ELK Elasticsearch?
The pricing for Elastic Search is mainly budgeted according to the organization budget, so we take it as a yearly subscription, and that is acceptable since we do get a fair discount when we are ta...
What needs improvement with ELK Elasticsearch?
When we get the logs, it is mostly about how we edit the configurations and how we make changes according to the requirements of our organization. In these cases, the logs sometimes can be a bit in...
What is your primary use case for ELK Elasticsearch?
I am the Elastic Search admin for my organization, and we are using Elastic Search to handle the traffic to GCP. The monitoring of all the clusters and all the deployments are quite good, and compa...
What needs improvement with IBM InfoSphere Information Server?
We are using the on-premises version of IBM InfoSphere Information Server, but we feel that all new development is mainly for the cloud. We receive corrections of errors, but we do not see new func...
What is your primary use case for IBM InfoSphere Information Server?
My usual use case for IBM InfoSphere Information Server is ETL, where we take data from one source to another data warehouse solution.
What advice do you have for others considering IBM InfoSphere Information Server?
We are about to change our platform from IBM AIX to SUSE Linux, as our whole platform is changing, so everyone should change from IBM to SUSE Linux. It would be very difficult for us to have a diff...
 

Also Known As

Elastic Enterprise Search, Swiftype, Elastic Cloud
InfoSphere Information Server, IBM Information Server
 

Overview

 

Sample Customers

T-Mobile, Adobe, Booking.com, BMW, Telegraph Media Group, Cisco, Karbon, Deezer, NORBr, Labelbox, Fingerprint, Relativity, NHS Hospital, Met Office, Proximus, Go1, Mentat, Bluestone Analytics, Humanz, Hutch, Auchan, Sitecore, Linklaters, Socren, Infotrack, Pfizer, Engadget, Airbus, Grab, Vimeo, Ticketmaster, Asana, Twilio, Blizzard, Comcast, RWE and many others.
Canadian National Railway Company, Chickasaw Nation Division of Commerce, Swedish Armed Forces, BG RCI, Janata Sahakari Bank Ltd., University of Arizona, Biogrid Australia
Find out what your peers are saying about Amazon Web Services (AWS), Informatica, Palantir and others in Cloud Data Integration. Updated: September 2026.
915,341 professionals have used our research since 2012.