Likelihood to Recommend If you are truly using IBM API Management for an API gateway, you will be ok. if you start trying to build custom scripts to transform messages complex in nature, it will soon become unmanageable.
Read full review 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.
Read full review Pros Import APIs - We have an existing inventory of APIs and services, so having an easy import process was required. IBM provides the ability to import Swagger so the process was quick and easy. Service Offerings - Can create plans to control various model offerings for varying clients depending on the need. You are not locked into a tier structure and can customize if a need arises. API Usage - visibility into the use of an API with a wealth of reporting information allows you to support an API from a production use to trending and forecasting any future growth. Read full review Easy access to any type of source system. Data could be in any format. Very beautiful visual representation of transforms that makes it super easy to use it by any non developer. It can be run in cloud or on-premise. helping you choose your comfort of security. Has pretty good customer support and have recently started their community forum as well. Read full review Cons Troubleshooting deployment pipeline - identifying issues with your api based on restrictions through a deployment pipeline is difficult. If a quality assurance environment is less stringent than a production environment, making sure your api is accessible and configured appropriately is tough. Code level scripting is limited to javascript and xslt. so if any complex fanning needs to occur, you are limited in tooling. Administration is more cumbersome than it needs to be. There are roles/profiles that are defined, but to use a group email for the approval or use of an api needs to managed better. A more thorough thought process needs to be defined - which I think IBM is tackling as an improvement. Read full review They need to have a way to connect to GitHub to allow the users to maintain their version control in GitHub. This is a missing functionality. As pipelines become complex, it's difficult to have all the snaps stitched together - just like to see it done differently. They do not have a way to start/stop a preview. This is hard to use, especially if you have to stop an accidental preview invocation. Read full review Likelihood to Renew 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!
Read full review Usability It is very powerful but has a steep learning curve
Read full review Support Rating 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.
Read full review Implementation Rating The groundplex in our VPC is very nice for security reasons and the SnapLogic team was extremely helpful during our implementation
Read full review Alternatives Considered There are a lot of similarities between
Apigee Edge and IBM API Management. Some of the differences at the time of this posting is... 1) IBM APIM/C integrates better with other products. Dynatrace is used to track API and service specifics with the ability to offload those statistics for operational reporting. 2) If you are evolving from DataPower, IBM API Management is a logical choice to support additional REST APIs. 3) Generating keys is simple. Integration of those keys with a secure data vault is easy as well for your consumer.
Read full review We opted for SnapLogic due its ease of use and the flexibility it offers, it was the platform that was strongest in both application integration and data integration and both were use cases we wanted to be able to cover.
Read full review Return on Investment Centralizing on an API management platform was imperative. Being able to support SOAP UIs as well as REST APIs was required. Because of the tooling, service inventory and provisioning can be managed - regardless of the pricing and cost structures are used. Constructing plans that provide tiering options based on rate limits help in onboarding new consumers. The lesser cost in onboarding through an API gateway outweighs the cost of modifying/configuring an API to handle multiple clients. Defining guidance and onboarding practices while rolling out the product also helps in the adoption, reference architecture, and governance that can save your company money. Read full review We have cut development time down by at least 70% The software was more on the expensive side at renewal which required some further approvals to be sought for the spend More developers are able to build and use Snaplogic pipelines in their projects Read full review ScreenShots