Likelihood to Recommend 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 We don't use webMethods.io Integration for scenarios where we need to integrate to on-premises legacy applications that have limited support for modern security controls such as OAuth 2.0 and transport encryption. Likewise, we don't use it for solutions that involve any of our systems that are controlled by safe-working processes. For those scenarios, of which we have many, we maintain on-premises webMethods Integration Server and Trading Networks instances to build and execute and support and monitor those solutions. This then requires us to hook our on-premises integration platform up to the webMethods.io Integration cloud, to ship messages between the two integration platforms. This all begs the question if a cloud solution cannot be used for all use cases or scenarios that the business has, then why add the complexity of using the cloud at all if you still need to maintain an on-premises solution to support the non-cloud appropriate scenarios.
Read full review Pros 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 Easy to use Priced competitively Supports robust and resilient integration solutions Read full review Cons 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 Complex logic is hard to understand in simple diagrammatic user interface User interface too simplistic for solutions that are complicated or go against the grain Runtime observability could be improved 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 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 webMethods.io IntegrationDescriptionWe uses webMethods.io Integration to solve some of our application to applications and business to business integration needs. It is the Integration Platform as a Service solution that we use in a mix with our continued use of webMethods Integration Server and Trading Networks on-premises. For any solutions that meet the use cases that we deem an appropriate fit for running in the cloud, we build those solutions using webMethods.io Integration. More specifically, we use webMethods.io Integration to synchronize changes in one application or system, in another application or system, by shipping data mutations via integration messaging and API calls. We also use webMethods.io Integration to integrate with external organizations. Our trading partners and supply chain partners provide APIs that we consume, and vice versa, to notify each other of business process events as they occur in the respective organizations. Please provide some detailed examples of things that webMethods.io Integration (webMethods Integration Cloud) does particularly well. Easy to usePriced competitivelySupports robust and resilient integration solutions please provide some detailed examples of areas where webMethods.io Integration (webMethods Integration Cloud) has room for improvement. These could be features that are hard to use, missing functionality, or just things that you'd like to see done differently. Complex logic is hard to understand in a simple diagrammatic user interface too simplistic for solutions that are complicated or go against the gain runtime observability could be improved please describe some specific scenarios based on your experience where webMethods.io Integration (webMethods Integration Cloud) is well suited, and/or scenarios where it is less appropriate. We don't use webMethods.io Integration for scenarios where we need to integrate to on-premises legacy applications that have limited support for modern security controls such as OAuth 2.0 and transport encryption. Likewise, we don't use it for solutions that involve any of our systems that are controlled by safe-working processes. For those scenarios, of which we have many, we maintain on-premises webMethods Integration Server and Trading Networks instances to build and execute and support and monitor those solutions. This then requires us to hook our on-premises integration platform up to the webMethods.io Integration cloud, to ship messages between the two integration platforms. This all begs the question if a cloud solution cannot be used for all use cases or scenarios that the business has, then why add the complexity of using the cloud at all if you still need to maintain an on-premises solution to support the non-cloud appropriate scenarios. What positive or negative impact (i.e. Return on Investment or ROI) has webMethods.io Integration (webMethods Integration Cloud) had on your overall business objectives?webMethods.io Integration is a cost-effective approach to integration in isolationwebMethods.io Integration as a supplement to on-premises integration is pointless and redundant and just adds complexity to the environment and additional costswebMethods.io Integration is a tough sell for organizations using Microsoft Azure integration products such as Logic AppswebMethods.io Integration has a faster time to market where the use case means standard provided adapters can be used describe how webMethods.io Integration (webMethods Integration Cloud) stacks up against them and why you selected webMethods.io Integration (webMethods Integration Cloud). For any organization which is already using Software AG products on-premises, such as webMethods Integration Server and Trading Networks, or Universal Messaging, evaluating and using webMethods.io Integration is the path of least resistance. It will be incredibly easy for your webMethods team to get up to speed on how to use webMethods.io Integration, and start developing new solutions on it. However in my opinion you should only add cloud to your integration product portfolio if you believe you can move 100% of your integration needs to the cloud. Otherwise, you will need to maintain an on-premises integration solution anyway, which means you end up with a more complex IT landscape by adding cloud to supplement on-premises integration for little benefit in terms of cost, complexity, and resourcing requirements. For organizations that are not already a Software AG shop, you should evaluate webMethods.io Integration on its merits, however, it's usually the right decision to double down on your existing products and vendors if you have no big issues with the current state. This is to say that if you are a Microsoft shop then adding Azure cloud products to your portfolio is pretty much inevitable, and avoiding the complexity of multiple clouds should also be something organizations consider.
Read full review Return on Investment 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 webMethods.io Integration is a cost effective approach to integration in isolation webMethods.io Integration as a supplement to on-premises integration is pointless and redundant and just adds complexity to the environment and additional costs webMethods.io Integration is a tough sell for organizations using Microsoft Azure integration products such as Logic Apps webMethods.io Integration has a faster time to market where the use case means standard provided adapters can be used Read full review ScreenShots