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

Elastic Search vs SAP Replication Server comparison

 

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
91
Ranking in other categories
Indexing and Search (1st), Cloud Data Integration (5th), Search as a Service (1st), Vector Databases (2nd)
SAP Replication Server
Average Rating
8.0
Reviews Sentiment
7.0
Number of Reviews
7
Ranking in other categories
Database Development and Management (20th), Data Integration (43rd)
 

Featured Reviews

Anurag Pal - PeerSpot reviewer
Technical Lead at a consultancy with 10,001+ employees
Search and aggregations have transformed how I manage and visualize complex real estate data
Elastic Search consumes lots of memory. You have to provide the heap size a lot if you want the best out of it. The major problem is when a company wants to use Elastic Search but it is at a startup stage. At a startup stage, there is a lot of funds to consider. However, their use case is that they have to use a pretty significant amount of data. For that, it is very expensive. For example, if you take OLTP-based databases in the current scenario, such as ClickHouse or Iceberg, you can do it on 4GB RAM also. Elastic Search is for analytical records. You have to do the analytics on it. According to me, as far as I have seen, people will start moving from Elastic Search sooner or later. Why? Because it is expensive. Another thing is that there is an open source available for that, such as ClickHouse. Around 2014 and 2012, there was only one competitor at that time, which was Solr. But now, not only is Solr there, but you can take ClickHouse and you have Iceberg also. How are we going to compete with them? There is also a fork of Elastic Search that is OpenSearch. As far as I have seen in lots of articles I am reading, users are using it as the ELK stack for logs and analyzing logs. That is not the exact use case. It can do more than that if used correctly. But as it involves lots of cost, people are shifting from Elastic Search to other sources. When I am talking about pricing, it is not only the server pricing. It is the amount of memory it is using. The pricing is basically the heap Java, which is taking memory. That is the major problem happening here. If we have to run an MVP, a client comes to me and says, "Anurag, we need to do a proof of concept. Can we do it if I can pay a 4GB or 16GB expense?" How can I suggest to them that a minimum of 16GB is needed for Elastic Search so that your proof of concept will be proved? In that case, what I have to suggest from the beginning is to go with Cassandra or at the initial stage, go with PostgreSQL. The problem is the memory it is taking. That is the only thing.
reviewer1834542 - PeerSpot reviewer
Finance Business Process Improvement, Transformation and Project Management at a consultancy with self employed
Eliminates replication and allows you to use only one database, speeding up performance and reducing amount of storage
The private solution is expensive. If you're in a situation where you're paying IBM or AWS or somebody just to host you specifically, you're paying people to run it and you're taking care of all the upgrades. As a company, you're either hiring or paying an outsourcer to do that, and you have to manage it, keep up with the updates to the hardware, software, and the operating system. It's very expensive because there's a lot to control and take care of.

Quotes from Members

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

Pros

"The fact that you can dump any type of format in the database without any specific reformatting is fantastic."
"A positive feature of ELK is that it directly interacts with Elasticsearch, the UI is very nice, and performance wise it's quite good too."
"From a technical point of view, there are no significant issues recalled as Elastic Search has been absolutely awesome for this use case and covers 100% of the needs."
"The tool's stability and performance are good."
"There's lots of processing power. You can actually just add machines to get more performance if you need to. It's pretty flexible and very easy to add another log. It's not like 'oh, no, it's going to be so much extra data'. That's not a problem for the machine. It can handle it."
"The most valuable features of Elastic Enterprise Search are it's cloud-ready and we do a lot of infrastructure as code. By using ELK, we're able to deploy the solution as part of our ISC deployment."
"Data indexing of historical data is the most beneficial feature of the product."
"It is easy to scale with the cluster node model.​"
"Currently, there is a Hadoop-based infrastructure with several engineers to maintain the data, and now, using SAP Replication Server, it has become automatic and requires fewer people to put data in the data warehouse."
"SAP is renovating different things. We are using external tools to connect as of now. It is going well, and now the new generation integration platforms are going to be pretty easy."
"SAP Replication Server is an application that I consider to be a robust system. It has proven to be highly reliable in my experience."
"This product has a catalog with the location of all the objects which were replicated, and it's very simple to maintain."
"It's pretty good at handling replication, even under high load. It also provides cross-database replication, for example, from Sybase to Oracle."
"It speeds up the performance in terms of how fast you are able to access the data, look at it, get it reported to you, and send it to somebody. It also reduces the amount of storage."
"The most valuable thing about this product is that it replicates data between SAP databases (ASE to IQ) very successfully."
"We can customize any workflow and we also like the business domain modeling that can be done."
 

Cons

"There were also some difficult times with parallel and point-in-time interfaces, so better documentation could help, particularly more example-driven content."
"I think the GUI part of the solution has the most room for improvement."
"The one area that can use improvement is the automapping of fields."
"Elasticsearch should have simpler commands for window filtering."
"The metadata gets stored along with indexes and isn't queryable."
"To do what we want to do with Elastic Search, the queries can get complex and require a fuller understanding of the DSL."
"From the UI point of view, we are using most probably Kibana, and I think they can do much better than that."
"There are potential improvements based on our client feedback, like unifying the licensing cost structure."
"It's a very expensive solution."
"If someone wants to replicate their data from Sybase to a newer technology for data warehousing or other purposes, it would be better if they supported those."
"It's complex. It's necessary to understand a little about infrastructure, like network LAN and VLAN environment."
"The private solution is expensive. If you're in a situation where you're paying IBM or AWS or somebody just to host you specifically, you're paying people to run it and you're taking care of all the upgrades."
"Setup was a little complex."
"Improvement is a never ending story, and HANA is doing some improvements. We are able to adopt that, and we have to do it by integration with HANA. They are very major changes that we need to see."
"I would like to see it become mobile-friendly."
"There is a need to improve performance in high transactional processes."
 

Pricing and Cost Advice

"We are using the open-sourced version."
"The pricing model is questionable and needs to be addressed because when you would like to have the security they charge per machine."
"We use the free version for some logs, but not extensive use."
"Elastic Search is open-source, but you need to pay for support, which is expensive."
"Although the ELK Elasticsearch software is open-source, we buy the hardware."
"An X-Pack license is more affordable than Splunk."
"We are using the free open-sourced version of this solution."
"The price could be better."
"You can pick one of the hosted cloud services as opposed to owning it and doing it yourself. Your cost of ownership on the hardware, the data storage, and the maintenance all go down. It depends on what service you use."
"It's a very expensive solution."
report
Use our free recommendation engine to learn which Cloud Data Integration solutions are best for your needs.
885,376 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
11%
Computer Software Company
10%
Manufacturing Company
9%
Retailer
7%
Construction Company
17%
Retailer
10%
Financial Services Firm
8%
Outsourcing Company
8%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business38
Midsize Enterprise10
Large Enterprise46
By reviewers
Company SizeCount
Small Business2
Midsize Enterprise1
Large Enterprise5
 

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?
On the subject of pricing, Elastic Search is very cost-efficient. You can host it on-premises, which would incur zero cost, or take it as a SaaS-based service, where the expenses remain minimal.
What needs improvement with ELK Elasticsearch?
From the UI point of view, we are using most probably Kibana, and I think they can do much better than that. That is something they can fine-tune a little bit, and then it will definitely be a good...
What needs improvement with SAP Replication Server?
SAP can provide better support for cross-database replication to newer technologies. The product supports Oracle, but I am not aware of what other technologies it supports. If someone wants to repl...
What is your primary use case for SAP Replication Server?
It's basically to transfer data from one server to another. It's used for this purpose.
 

Also Known As

Elastic Enterprise Search, Swiftype, Elastic Cloud
Sybase Replication 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.
Medtronic, Cirque du Soleil, Antarc, B&G Manufacturing, EarlySense, eBay, Ferrero, James Austin Company, Lenovo, Sagem, RAK Ceramics, Vodafone
Find out what your peers are saying about Elastic Search vs. SAP Replication Server and other solutions. Updated: March 2026.
885,376 professionals have used our research since 2012.