SAP Replication Server vs SnapLogic comparison

"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's pretty good at handling replication, even under high load. It also provides cross-database replication, for example, from Sybase to Oracle."

"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 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 feature I found most valuable in SnapLogic is low-code development. Low-code development has been very useful for simple processes, which is required for business users such as extracting details from a file or getting things reported by calling your web service. Calling your web service also becomes easier with SnapLogic because of the snaps available, so if you have the documentation, you can call an API. You don't have to write all those clients to call an API, so that is another feature I found very easy in SnapLogic. Configuring and managing all the file systems also become very handy with the solution."

"I find the reusability and the snaps to be very valuable features."

"The solutions ability to connect "snaps" or components to the graphic user interface is very intuitive, prevents errors, and makes implementations easy."

"SnapLogic positively impacts my organization, mainly in three areas: speed, system reliability, and maintainability."

"An important tool for building prototypes and MVPs than can seamlessly turn into production jobs"

"I find SnapLogic to be user-friendly, especially for beginners with limited experience in data engineering or ETL."

"I found SnapLogic valuable and what I found most valuable about it was its ETL feature. I also found its automation feature valuable. It can be used for automating manual activities. It can be used as a middleware for certain transactional data processing and minimal datasets and ETL activities."

"The API architecture makes it easy for orchestration."

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

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

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

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

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

"Ultra Pipelines provides real-time ingestion but it needs some adjustment."

"Sometimes there are glitches when moving a design pipeline from the development to production environment."

"We'd like zero downtime in the future."

"The solution isn't ideal for complex processing or logic. We use another solution for that."

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

"Connecting to data behind enterprise firewalls has been tricky."

"It's a very expensive solution."

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

"The pricing is okay."

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

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

"The license model is based on consumption."

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

"SnapLogic's price is high compared to the other tools available in the market."

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

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