Amazon API Gateway vs. SnapLogic

Experienced a lack of available programming languages while working on a minor project. I had to halt the project and wait for it to be added later. It took ages and had a hit on our productivity. It has a centralized management system which helps and an easy interface which helps to manage multiple tasks in case of large-scale operations and projects.

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.

• API Gateway integrates well with AWS Lambda. This allows us to build a web server in the language and framework of our choice, deploy it as a Lambda function, and expose it through API Gateway.
• API Gateway manages API keys. Building rate limiting and request quota features are not trivial (or interesting).
• API Gateway's pricing can be very attractive for services that are accessed infrequently.

Incentivized

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

Incentivized

• Client certificates are troublesome when trying to attach them to API GW stages.
• Debugging across several services can be difficult when API GW is integrated with Route 53 and another service like Lambda or EC2/ELB.
• Creating internal/private APIs, particularly with custom domains, can be unintuitive.

Incentivized

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

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 a great product very reliable and stable for connecting various aws services like we connected with lambda function and it is working very well, never faced any issue after the setup. It also saves out lots of money as well as time after we implemented the automatic ec2 server recovery system

Incentivized

It is very powerful but has a steep learning curve

Incentivized

We always had a great experience with the AWS support team. They were always on time and very dependable. It was a good partnership while we worked to resolve our issues.

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

When we tested Azure API Management at the time, it had serious connectivity issues, it was very unstable, and it needed to do a lot using the command line. Comparing with the AWS solution, which was more mature, and the fact that we have services in use on AWS, we ended up choosing to continue using AWS products. This so as not to run the risk of increasing latency in accesses, and of some functionality not working, due to being developed yet.

Incentivized

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.

• ROI is negative, you need either to hire them to work with you or spend days/weeks to figure out issues.
• For some of the projects in the end it is not worth it, it is just a "buzz" to use serverless but not practical.
• Service is easy to set up authorization and it is easy to manage.

Incentivized

• 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

Incentivized