Try our new research platform with insights from 80,000+ expert users

Elastic Search vs IBM Cloud Pak for Integration comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Dec 3, 2024

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
Ranking in Cloud Data Integration
9th
Average Rating
8.2
Reviews Sentiment
6.8
Number of Reviews
71
Ranking in other categories
Indexing and Search (1st), Search as a Service (1st), Vector Databases (3rd)
IBM Cloud Pak for Integration
Ranking in Cloud Data Integration
15th
Average Rating
8.6
Reviews Sentiment
7.0
Number of Reviews
5
Ranking in other categories
API Management (26th)
 

Mindshare comparison

As of July 2025, in the Cloud Data Integration category, the mindshare of Elastic Search is 2.1%, up from 0.6% compared to the previous year. The mindshare of IBM Cloud Pak for Integration is 2.1%, up from 1.9% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Cloud Data Integration
 

Featured Reviews

Anand_Kumar - PeerSpot reviewer
Captures data from all other sources and becomes a MOM aka monitoring of monitors
Scalability and ROI are the areas they have to improve. Their license terms are based on the number of cores. If you increase the number of cores, it becomes very difficult to manage at a large scale. For example, if I have a $3 million project, I won't sell it because if we're dealing with a 10 TB or 50 TB system, there are a lot of systems and applications to monitor, and I have to make an MOM (Mean of Max) for everything. This is because of the cost impact. Also, when you have horizontal scaling, it's like a multi-story building with only one elevator. You have to run around, and it's not efficient. Even the smallest task becomes difficult. That's the problem with horizontal scaling. They need to improve this because if they increase the cores and adjust the licensing accordingly, it would make more sense.
Igor Khalitov - PeerSpot reviewer
Manages APIs and integrates microservices with redirection feature
IBM Cloud Pak for Integration includes monitoring capabilities to track the performance and health of your integrations. You can quickly roll back to a previous version if an issue arises. Additionally, it supports incremental deployments, allowing you to shift traffic to a new version of an API gradually. For example, you can start by directing 10% of traffic to the new version while the rest continue using the legacy version. If everything works as expected, you can gradually increase the traffic to the new version over time. IBM Cloud Pak for Integration has a client base that includes numerous organizations using AI and machine learning technologies. We leverage an open-source machine learning framework and integrate it with Kafka to help create and manage various products and data retrieval processes. For companies with private data, the framework first retrieves relevant data from a GitHub database, which is then combined with the final request before being sent to a language model like GPT. This ensures that the language model uses your specific data to generate responses. Kafka plays a key role by streaming real-time data from file systems and databases like Oracle and Microsoft SQL. This data is published to Kafka topics, then vectorized and used with artificial intelligence to enhance the overall process. It's like an old-fashioned approach. The best way is to redesign it with products such as Kafka. Overall, I rate the solution an eight out of ten.

Quotes from Members

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

Pros

"The most valuable features are the ease and speed of the setup."
"You have dashboards, it is visual, there are maps, you can create canvases. It's more visual than anything that I've ever used."
"It is a stable and good platform."
"The initial setup is very easy for small environments."
"Overall, considering key aspects like cost, learning curve, and data indexing architecture, Elasticsearch is a very good tool."
"I appreciate that Elastic Enterprise Search is easy to use and that we have people on our team who are able to manage it effectively."
"Elastic Enterprise Search is scalable. On a scale of one to 10, with one being not scalable and 10 being very scalable, I give Elastic Enterprise Search a 10."
"A nonstructured database that can manage large amounts of nonstructured data."
"The most preferable aspect would be the elimination of the command, which was a significant improvement. In the past, it was a challenge, but now we can proceed smoothly with the implementation of our policies and everything is managed through JCP. It's still among the positive aspects, and it's a valuable feature."
"Redirection is a key feature. It helps in managing multiple microservices by centralizing control and access."
"The most valuable aspect of the Cloud Pak, in general, is the flexibility that you have to use the product."
"It is a stable solution."
"Cloud Pak for Integration is definitely scalable. That is the most important criteria."
 

Cons

"The real-time search functionality is not operational due to its impact on system resources."
"The one area that can use improvement is the automapping of fields."
"The documentation regarding customization could be better."
"The reports could improve."
"Elastic Enterprise Search could improve its SSL integration easier. We should not need to go to the back-end servers to do configuration, we should be able to do it on the GUI."
"An improvement would be to have an interface that allows easier navigation and tracing of logs."
"It should be easier to use. It has been getting better because many functions are pre-defined, but it still needs improvement."
"We have an issue with the volume of data that we can handle."
"The pricing can be improved."
"Enterprise bots are needed to balance products like Kafka and Confluent."
"Setting up Cloud Pak for Integration is relatively complex. It's not as easy because it has not yet been fully integrated. You still have some products that are still not containerized, so you still have to run them on a dedicated VM."
"The initial setup is not easy."
"Its queuing and messaging features need improvement."
 

Pricing and Cost Advice

"The solution is less expensive than Stackdriver and Grafana."
"We are using the free open-sourced version of this solution."
"We are paying $1,500 a month to use the solution. If you want to have endpoint protection you need to pay more."
"We are using the open-sourced version."
"The premium license is expensive."
"The solution is free."
"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."
"To access all the features available you require both the open source license and the production license."
"The solution's pricing model is very flexible."
"It is an expensive solution."
report
Use our free recommendation engine to learn which Cloud Data Integration solutions are best for your needs.
861,803 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
15%
Financial Services Firm
14%
Manufacturing Company
9%
Government
9%
Financial Services Firm
21%
Computer Software Company
10%
Government
9%
Insurance Company
8%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
 

Questions from the Community

What do you like most about ELK Elasticsearch?
Logsign provides us with the capability to execute multiple queries according to our requirements. The indexing is very high, making it effective for storing and retrieving logs. The real-time anal...
What is your experience regarding pricing and costs for ELK Elasticsearch?
We used the open-source version of Elasticsearch, which was free.
What needs improvement with ELK Elasticsearch?
It would be useful if a feature for renaming indices could be added without affecting the performance of other features. However, overall, the consistency and stability of Elasticsearch are already...
What do you like most about IBM Cloud Pak for Integration?
The most preferable aspect would be the elimination of the command, which was a significant improvement. In the past, it was a challenge, but now we can proceed smoothly with the implementation of ...
What needs improvement with IBM Cloud Pak for Integration?
Enterprise bots are needed to balance products like Kafka and Confluent.
What is your primary use case for IBM Cloud Pak for Integration?
It manages APIs and integrates microservices at the enterprise level. It offers a range of capabilities for handling APIs, microservices, and various integration needs. The platform supports thousa...
 

Also Known As

Elastic Enterprise Search, Swiftype, Elastic Cloud
No data available
 

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.
CVS Health Corporation
Find out what your peers are saying about Elastic Search vs. IBM Cloud Pak for Integration and other solutions. Updated: July 2025.
861,803 professionals have used our research since 2012.