SAP Replication Server vs SnapLogic comparison

"We can customize any workflow and we also like the business domain modeling that can be done."

"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."

"It's pretty good at handling replication, even under high load. It also provides cross-database replication, for example, from Sybase to Oracle."

"SAP Replication Server is an application that I consider to be a robust system. It has proven to be highly reliable in my experience."

"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 technical support from SnapLogic is excellent, and I would give it a complete ten."

"SnapLogic is an IPA tool that leverages a low code environment to connect to multiple sources, extract data, and store it in Azure data lake."

"SnapLogice is a low-code development tool."

"SnapLogic is more user-friendly than Boomi in terms of debugging. You can move the mouse to a place, and it will record and show the data easily."

"What I found most valuable in SnapLogic is the ETL feature, particularly the Transform Snap Pack, for example, any kind of reading or writing on Transform Snaps. Other than that, all the third-party connectivity tools such as the SAP Snap Pack, Salesforce Snap Pack, Workday Snap Pack, even the ServiceNow Snap Pack, I find all those are pretty useful in SnapLogic."

"The vendor handles the maintenance of the solution"

"By using snaps instead of functions in code, you can see the building blocks of the integration visually. This helps a lot."

"The API architecture makes it easy for orchestration."

"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."

"I would like to see it become mobile-friendly."

"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."

"There is room for improvement in terms of pricing and faster support."

"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."

"The support is the most important improvement they could make."

"I don't think the support has better knowledge about technologies and tool support. There were lots of times when we had an issue, and it took me quite a long time to explain the problem. I feel like some of the support staff don't know their product well."

"What could be improved in SnapLogic is that it was not capable in terms of processing a large number of datasets, but at that point, SnapLogic was evolving. It didn't give a lot of Snaps. I heard recently there are a lot of Snaps getting added and the solution was being enhanced, particularly to connect different data sources. When I was working with SnapLogic six months to one year back, I faced the issue of it not being capable of handling a huge volume of datasets or didn't have much of Snaps, and that was the drawback. If there is any large number of data sets, that's based on or depends on your configuration. If it is a huge volume of data, other traditional ETL tools such as Informatica and Talend can process millions and billions of records, while in SnapLogic, the Snaplex fails or it returns an error in terms of processing that huge volume of data. Informatica, Talend, or any other ETL tool can run for hours in terms of jobs, while SnapLogic jobs fail when the threshold is reached. SnapLogic isn't able to withstand processing, but I don't know if that's still an issue at present, because the solution is getting enhanced and it's been more than six months to one year since I last worked with SnapLogic. There are now a lot of Snaps getting added to the solution, and if it can overcome the limitations I mentioned, SnapLogic could be the go-to tool because currently, it's not being used as much in organizations. It's being used comparatively less compared to other retail tools."

"One of the areas for improvement in SnapLogic is that the connectors for some of the applications should be more available in terms of testing in the dev environment. Another area for improvement is that the logging should be standardized, for example, the integration with an ELK stack should be required out-of-the-box, so you can ship the log and have it in the ELK stack. There should be integration with ELK stack for the log shipping."

"The setup cost would be four or five. There would be only one point of improvement if the price could be lower."

"While new features are always welcome, I do not have anything else at the top of my mind currently."

"I find the learning curve for complex transformations, the debugging experience, performance optimization visibility, cost for small teams, and version control and DevOps integration could be improved in SnapLogic."

"SnapLogic should have some inbuilt protocol mechanism in order to speed up."

"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."

"It is a higher initial cost than other easy-to-use integration apps."

"I used the free trial."

"The cost with SnapLogic is an annual license and better than Informatica."

"When comparing it with solutions like Apigee or MuleSoft, it still offers better value."

"From the ROI perspective, the price is extremely high"

"The license model is based on consumption."

"They have pricing/usage tiers that are easy to move up or down."

"By scaling the solution incrementally the cost is controlled and more beneficial to the client."