Azure API Management vs. SnapLogic

The range of policies that enable the APIs to loosely couple it with security, rate limit, retry, etc. are good. We can easily tie authentication mechanisms to external and other internal services without having to modify the backend.

Incentivized

Snaplogic is unique from other IPASS tools if you're very sensitive about data security as they have an on-premise option where your data never needs to leave your data center. And data pipelines can be quickly created if Snaplogic has the requisite connector to your data sources. On the downside, if you're transforming a large amount of data for example in training machine learning models, a tool with elastic compute capability is more appropriate.

• Management of APIs
• Security of the API through Azure AD, AD B2C etc.
• Providing an outer layer through APIs

• Their customer service response time is brilliant.
• SFTP tasks do a great job in reading the file directly from the server, instead of having to download it and then read it.
• Tasks expose the ability to run them using external job schedulers.
• Once you have a server up, setting up SnapLogic service does not take long. They have good documentation and customer support too.

Incentivized

• Cost - the upfront cost is a bit restrictive. I've been told it is because there are a few underlying VMs that are running this service. So if you're just starting out with API management, it can be an expensive proposition. Value increases as you add additional APIs. If you're using Azure B2C for the developer portal, you'll require Standard or Premium since they support AAD integration.
• Security granularity - at time of writing, APIM doesn't support breaking out operations to products. For example, if you have an API that has a GET and a POST operation, and you want the POST operation to require a different subscription. There is a work around, but it makes management a bit messy.
• Developer and Publisher portal - it's a little weird. Microsoft hasn't migrated all the publisher portal functionality into the "native" Azure portal. So some of it feels a little weird - especially when working with the content management side of things for the developer portal.
• Scaling - while it's easy to scale up, the cost of APIM ramps up very quickly. Standard -> Premium is a 4x jump.

Incentivized

• Git integration outside of Github (Bitbucket, and other git service providers)
• I would like to see an improved way to perform unit testing within the SnapLogic framework, as opposed to the manual approach
• I would prefer that the underlying source of SnapLogic pipelines be more human-readable, although it is a GUI approach to authoring pipelines

Incentivized

This has been hands down the BEST software company I have ever used and dealt with. I am a 25 year IT veteran at this college. They go above and beyond in soliciting our feedback/input and proactively follow up about bugs, issues, etc. I have given multiple potential clients my thoughts and after seeing the SL demo they all sign up. I appreciate their support model, it's REFRESHING!

Incentivized

It is very powerful but has a steep learning curve

Incentivized

They can be prompt but they have not been as useful as I've wanted. We had a bug that affected many of our customers through an API connection between SnapLogic and our platform. Eventually they were able to figure it out, but it took a long time of negotiating between our engineering team and theirs. Additionally, we installed the SnapLogic groundplex for our customers and we've run into a bunch of problems of connectivity. If SnapLogic offered to be on those calls with our clients to troubleshoot how to fix these problems, I would give them a better grade here.

Incentivized

The groundplex in our VPC is very nice for security reasons and the SnapLogic team was extremely helpful during our implementation

Incentivized

Azure APIM vs Amazon API Gateway:

1) Azure APIM was a complete package that included a developer portal.

2) We are very Microsoft centric - so the Microsoft product suite aligned very well with our business needs.

3) It was faster and easier to stand up Azure APIM for testing than it was for the Amazon API Gateway.

Incentivized

Boomi was our runner-up product. The pricing model was much higher and cost-prohibitive. They were not as flexible with pricing on a non-profit higher education institution. We did love their integration code library shared across all clients. The user interface was on par with Snaplogic as well as the features that come included. Overall, seemed like a solid product just found something better for a lower price point.

Incentivized

• It’s really pay as you go, so it's not that costly to get in and try it out. There’s no expensive client to buy and manage, but you do need to stay on top of the rapidly changing Azure environment to be sure you upgrade or adjust when needed.
• It’s not great having more than one API tool, but it’s ok to spread out your work, as you always want the right tool for the right job. For example, if you are a Salesforce-heavy organization, I’d go with Mule over Azure.
• It was easy getting an external consultant access to the tool to build their own API for a project they were working on for us.

Incentivized

• We had a positive impact at our organization where handful of developers were able to integrate more than 50 systems in less than a year. It has helped us a lot by providing access to data that was previously not possible or unimaginable or get in such easy format.
• The only place where it didn't have a positive impact was for a realtime application integration project requiring on the fly aggregations, wherein this tool claimed it could do it but wasn't able to.

Incentivized