Microsoft System Center Orchestrator vs SnapLogic comparison

"Automation is the most valuable feature of the solution."

"It can manage multiple servers and workstations from a single location."

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

"The solution is easy to implement and easy to use. It's basically just drag and drop."

"The connection with SOAP is the best feature."

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

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

"The API architecture makes it easy for orchestration."

"You can use other languages, such as Python, and easily connect to other systems."

"The solution could improve its API management."

"I find the Orchestrator UI to be problematic."

"The product's management aspect needs enhancement."

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

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

"One area for improvement in SnapLogic is the transparency in the flow of data. It needs to have more transparency. Right now, users only have a preview option at the end of any job flow, so at the end of any Snap Pack, there is a data preview option that lets you review the data and see how it's moving. What would make the solution better is more debugging and more access to change data from the preview panel or more functionality in terms of the preview option."

"SnapLogic doesn't provide any on-premises software, so users have only cloud-based software to use."

"While it performs well, there is some room for improvement in this area."

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

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

"We obtained a license that bundled Windows Server with System Center at no additional cost."

"I give the cost of the solution a five out of ten."

"The pricing is okay."

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

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

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

"SnapLogic is not expensive. It's reasonably priced."

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

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

"The license model is based on consumption."