Marg SnapLogic

The some simple integrations can be built quickly.

- That complex integrations are made more difficult by the way Snaps interact.

- The lack of customisation available out the box.

- The dependency on a link to the cloud at all times, otherwise scheduled integrations don't run (unless you pay for ultra).

- The price of Snap Packs.

- The amount charged for their other pricing model, where you pay by number of documents processed.

- The lack of API capabilities.

- The number of workarounds often required to design a generic, reusable integration.

- The lack of dedicated IDE.

- Requiring all development to be done via web browser.

- The lack of communication during patches.

- The slow response of their service desk.

- The lack of communication from their development team when issue found with their Snaps.

- The restrictions on Snaps often leading to scripting being used instead.

- The lack of flexibility surrounding refining security policies on the platform.

- The lack of granularity surrounding assigning permissions, only allowing permissions to be set on a project basis rather than down to an integration specific level.

- How most Snap Packs merely wrap the APIs provided from a service, i.e. JIRA, yet a premium price is charged for them.

- The general lack of empowerment for developers compared to other enterprise tools.

Recommendations to others considering the product:

What problems are you solving with the product? What benefits have you realized?

Response from Adrian Richardson of SnapLogic

We're terribly sorry to hear that! We'd be happy to help you through these concerns ASAP if you email customersuccess at snaplogic.com.

The visual interface, while not exclusive to SnapLogic, is easy to pick up and get started with.

There are many features available in other ETL tools that either require complicated work arounds to produce in SnapLogic or are simply not an option. The error handling is also quite complicated or provides little to no information.

What problems are you solving with the product? What benefits have you realized?

Response from Adrian Richardson of SnapLogic

Thank you for the feedback! We update our platform every quarter and would love to hear more from you - if you can email us at customersuccess at snaplogic.com, we can pick things up from there. Looking forward to hearing from you!

Data processing pipelines development is pretty convenient with Snaplogic.

It provides pretty many built-in components for basic and advanced data processing, data transformation, data movement etc with plenty of connectors to various data platforms.

It is possible to implement both simple data pipelines quickly, and pretty complex and complicated scenarios.

Business logic can be implemented with both built-in components and Python/JavaScript/Ruby scripts.

Debugging mode is extremely useful.

The main concerns are about reliability and tech support.

There's been rare case when we haven'd had an issue during regular Snaplogic platform release roll out. Usually there were issues with 'backward compatibility', meaning that previously valid pipelines become invalid, so we needed to fix them.

Since Snaplogic rolls out new release three or four times a year (don't remember exact number), it's almost guarantees that you've got an issue from the platform side this times per year.

Support experience didn't impress, keeping us waiting days and weeks with an issue unresolved.

Perhaps the most disappointing situation was when we faced an 'Snaplogic internal error' failure and had to wait pretty long time it to be investigated by the support team.

Recommendations to others considering the product:

What problems are you solving with the product? What benefits have you realized?