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.
$2,500
per month
monday.com
Score 8.3 out of 10
Mid-Size Companies (51-1,000 employees)
monday.com Work OS is an open platform designed so that anyone can create the tools they need to run all aspects of their work. It includes ready-made templates or the ability to customize any work solution ranging from sales pipelines to marketing campaigns, CRMs, and project tracking.
In any scenario where a distributed enterprise IT landscape needs a unified approach to solve the challenges of enabling a common information supply chain where different stakeholders as well as citizen developers can be empowered to contribute, participate and own their own parts of the integration landscape - IBM webMethods offers a capable, architecturally sound and cost efficient way of supporting a wide range of enterprise system integration needs.
The platform is very well suited for our nonprofit programs that serve low-income clients who need diapers, wipes, and period products. It has helped us run our programs, capturing information and allowing us to view the data for reporting purposes. The ability to filter data is very helpful by allowing us to categorize information to get a better picture of the progress of our programs.
I like summary of subitems, especially with subitasks as subitems and add item tracking for each subtask it can show total tracked in parent item. Similar with other columns, like numbers, status, date.
Dashboard features, Many kinds of dashboard view available, we can utilize on the basis of requirements.
monday.com workform is very powerful, easily share form link when submitted it will create line item in board with provided data.
monday.com automation is very helpful in order to automate steps with specific rules and easy setup.
monday.com also provides integrations in order to automate processes if need to integrate multiple app together. or need to transfer data between multiple apps.
The desktop app for Mac seems to have a few issues with visual glitches appearing on screen, it only seems to go away when I close the tool and reopen it
Subtasks don't show on the individual users to-do list, only main level tasks
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.
Teams involved in content creation, such as marketing or editorial teams, could use monday.com to manage the entire content lifecycle. Boards might track content ideas, assignments, drafts, reviews, approvals, and publication schedules, helping teams collaborate and keep content production on track.
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.
I give monday.com a 10/10 because I almost never encounter any lag or connectivity issues despite all of the many templates, boards, and automations we have. As a matter of fact, I feel like the last issue I encountered was over a year ago... and I'm in monday.com every single work day. Not only is monday trustworthy, it is easy to find what I'm looking for... making the overall usability extremely hard to beat.
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
Everything performs fairly well. Every now and then there are user errors where an employee will not click "ok" on a note they've created and simply exit out (I do wish that something was in place to prevent this, such as a pop "are you finished?")
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.
monday.com only really care about accounts that have 20 seats or more. While this is great for monday.com, it pushes smaller organisations to evaluate alternatives. We rate monday.com highly in our organisation because key staff have already got good experience with the application and we know we will get to 20+ seats one day. But, till then the billing model and lack of permanent enterprise features is a dread.
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
To have someone walk you thru the features and capabilities of Monday.com is priceless. Someone also coming along later in the contract to see if you are maximizing the program to suit your company needs is beyond helpful. The staff that have provided this training are fun, creative and very patient.
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.
We signed up for the accounts. Created the accounts. Ran the trial version and tested it live while we were running multiple projects and found that it was fitting our needs perfectly. When the trial ended and we were asked to purchase the full version, we did. We have found other ways to use it and it's a breeze.
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.
monday.com is simpler and easier to grasp, apply and navigate than ClickUp, but the ClickUp free version has so much more functionality available than the monday.com free / low-cost options (sorry, but it's true!). Google Tasks is really simple and I shouldn't really compare them - it's just really nice to be able to see my tasks right next to my Google Calendar or Gmail (widget) - the "all on one" view on the screen is really nice ease of access, but the power of monday.com outweighs the nice-to-have of an all-in-one screen layout - it feels clumsy to bring in all my Calendar items from Google to monday.com, so an integration app to the Google screen where you can see monday.com tasks would be amazing.
For it to work across multiple departments and sites, I would like to see improvements made with integrations and automation. For this question, I am acknowledging not only the addition of internal triggers/automation, but also an expansion on external ones.
