IBM® webMethods offers a hybrid, enterprise-grade integration platform as a service (iPaaS) that allows users to securely control applications, APIs, B2B and files across environments and locations.
N/A
SnapLogic
Score 6.9 out of 10
N/A
SnapLogic is a cloud integration platform with a self-service capacity supported by over 450 prebuilt modifiable connectors. SnapLogic also offers real-time and batch integration processes for interfacing with external data sources, a drag-and-drop interface, and use of the vendors’ Iris AI.
N/A
Pricing
IBM webMethods
SnapLogic
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
IBM webMethods
SnapLogic
Free Trial
No
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
Optional
Additional Details
—
—
More Pricing Information
Community Pulse
IBM webMethods
SnapLogic
Considered Both Products
IBM webMethods
Verified User
Anonymous
Chose IBM webMethods
IBM webMethods lags in terms of iPass offering as compared to mulesoft and dell Boomi. In terms of api management Apigee is much better than webMethods.
IBM webMethods is far superior when compared to competition like Microsoft Azure. In functionality and capabilities. Better visibility, uptime, efficiency, etc.
webMethods does better for end to end integrations whereas Azure is more focused on APIs. We selected webMethods because we felt their integrations, especially to mainframe environments, were much better than the others. IBM has been in this space for a long time and know it …
Oracle Integration Cloud vs IBM webMethods, hands down IBM webMethods is way better. Lots of features and ease of doing webMethods and super stable stack.
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 …
IBM webMethods was selected vs WSo2 for the reachness of the correspondign features regarding Mulesoft, the flexibility of IBM webMethods compared to the other platform, in relation to the existing architectural landscape was preferred
The two branches of the IBM integration portfolio are coming together nicely, and it's more a question of fully mapping the specific implementation requirements to the respective platform of choice when selecting between IBM Cloud Pak for Integration and IBM webMethods. …
I have seen that other products have different UI to address various business problems like messaging, EDA, MFT. IBM webMethods has unified platform and can also support hybrid Integration. I think it is all rounded iPaaS tool with ease of development and ease of operation. The …
The webMethods platform ranks higher in our ranking because it has more features and has proven itself in many CAC 40 companies in particular.The key elements are robustness, ease of use, a clear business model, and a wide range of features covering all types of enterprise …
IBM webMethods combines all the essential functions for information system integration in its platform. All products are interconnected to facilitate implementation (ESB, API, BPM, message bus). All tools are easy to use.
Other providers found it difficult to allow us to use their services on our cloud premises (exclusively in our AWS accounts) which we need for compliance. SnapLogic was able to give us this guarantee.
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 …
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.
The simple interface and ease of building the pipelines with "snaps" was a selling point for SnapLogic. Amongst the multitude of snap packs available with new ones constantly being added. The support and vendor engagement was also very pleasant. Although amongst the more …
SnapLogic suits my company's needs better than Scribe because it's a lot less complicated to move data between different systems, and the monitoring aspect is way better. Scribe does have better customer support though, as SnapLogic is a lot more hands-off. Scribe feels easier …
Snaplogic is great for what it is. It's not an all-inclusive solution. You likely don't need a snap license when you have one or two systems, or you don't have a centralized SQL database. Once you have multiple tools and you start automating reports you'll want a license to tie …
Earlier we used to work on this tool, but since SnapLogic came in the picture it gave us a lot of confidence to work faster, easier and in a more convenient way. So I would recommend using SnapLogic because of its simple functionality for smaller organizations. It is fast at …
SnapLogic does better API integration than Informatica Power Center. Informatica has better re-usable component integration and version control than Snaplogic. Metadata lineage for Informatica is better than SnapLogic. I do not think that SnapLogic is better than SSIS.
Snaplogic was much better than Boomi in the customer response time. In fact, this was one of the deal-breaker reasons. SnapLogic was better than Informatica in its ability to read directly from the sources/SFTP files instead of downloading them. Pentaho is great, but we wanted …
We selected SnapLogic because it paired really well with the two cloud systems we needed to move data between. The pre-built connecters allowed us to easily set up our pipelines to create the ETL of data between the two systems.
With its world-class proven technology, the IBM webMethods products are best suited for solving integration needs, including application connectivity, data aggregation, and data synchronization. The business use cases expand across Healthcare, Aviation, Banking, Insurance, etc., and many other mission-critical systems. Though I feel there is room for improvement where webMethods products are utilized in a containerized platform, especially with the API Management suite of products.
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.
The webMethods platform is a fantastic tool for modernizing information systems. It's easy to use and delivers rapid results.The platform is focused on innovation and is accelerating its improvement with the acquisition by IBM.
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!
The webMethods product has a very user-friendly and easy-to-use interface.A weak point is the My webMethods Server portal (administration and monitoring portal for the on-premise platform). This weakness has been addressed thanks to the control plane on the hybrid version of the product. This version should be highlighted and used to ensure a very fluid and functional interface.
The webMethods platform is very stable and does not cause incidents: if it is well configured and tailored at the base. Infrastructure incidents represent 20% of incidents (full disk, memory peaks, etc.) 80% of incidents come from the implementation of the code in the platform. If a code is not optimized and a high volume is observed in production, this can cause incidents. Similarly, if all error cases or conditions are not handled in the code, this can cause errors. Finally, there can be common errors if the applications connected to the platform do not return quality data or are unavailable.
The webMethods platform is designed to handle a high volume of small messages. It's a tool for continuous processing.The incidents I've seen involving application performance declines are caused by: - Code optimization issues - File size issues or fragmentation of the transmitted file - Misuse of the platform (batch processing) - Monitoring data was not purged, and the user was working with millions of data points
In the majority of the tickets I've created, support has been very responsive and provided the right solutions or solutions.Resolving a ticket also depends on the information provided by the creator. It's important to provide the technical context and information about the environment, as well as information to help the support team reproduce the incident.
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.
We received in-person training from the webMethods team. We received standard training from the vendor and custom training on specific security topics.The training sessions went well but remained very standard and did not adapt to the client's specific business. In-person training is more suitable for rapid skill development. It is necessary to practice for a few weeks to ensure familiarity with the tool.
I found clear and easy-to-follow training with realistic use cases for quick understanding and a 360° view of the features. The lesson format allows you to progress and learn by breaking down the allocated time.The technical courses are described step by step, allowing you to quickly get to grips with the products
When implementing webMethods, it's essential to have the right support and guidance.It's important to map out the interactions, document them, prepare test cases, and implement them while making maximum use of the product's native features.Additional tools must also be planned to automate deployments, visualize logs, and monitor the platform.
The two branches of the IBM integration portfolio are coming together nicely, and it's more a question of fully mapping the specific implementation requirements to the respective platform of choice when selecting between IBM Cloud Pak for Integration and IBM webMethods. Pricing and licensing model, cloud strategy, and level of distributed responsibilities and ownership of integration in the organisation can be deciding factors.
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.
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
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.
