We performed a comparison between AWS Step Functions and webMethods Integration Server based on real PeerSpot user reviews.
Find out what your peers are saying about Camunda, Apache, Pega and others in Business Process Management (BPM)."One can rate all the calls and that is a good feature."
"The number of historical events is great."
"It's a general solution that you can adapt to your own needs and is simple to use. We like that it can be integrated with everything in the AWS suite, and that the creation of the pipeline can be done using the graphical user interface."
"It is a scalable solution."
"It's Amazon, it's scalable."
"What I like the most about Amazon Step Functions is how easy it is to use."
"The solution is stable...The solution is easy to scale."
"AWS Step Functions acts as a high-level layer, allowing us to seamlessly integrate with microservices."
"The MFT component of webMethods, for example, is easy to set up and convenient to use. It handles files very efficiently and it is easy to automate tasks with complex schedules. Monitoring is centralized to MWS which can be used to monitor other products as well (Trading Networks, BPM, MFT, etc.)"
"A product with good API and EDI components."
"The solution has a very comprehensive and versatile set of connectors. I've been able to utilize it for multiple, different mechanisms. We do a lot of SaaS and we do have IoT devices and the solution is comprehensive in those areas."
"The messaging part is the most valuable feature."
"The product is very stable."
"Broker and UM are the best features."
"We have a reusable code that we can replicate for any new interfaces."
"The most valuable feature is stability."
"The price and support are areas with shortcomings where the solution needs to improve."
"I would like to see more data transformation features in Amazon Step Functions like additional operators and logic."
"The interface can sometimes feel limited, as we're unable to see what AWS is running behind the scenes."
"The pricing of the solution can be improved."
"It wasn't easy to understand the licensing model. It's like if you use just a little, it's cheap, but it becomes more expensive as you use more. It's like a hook that ties you inside the Amazon ecosystem. So, it creates a dependency."
"The solution's data size limit can be improved."
"It is hard to coordinate the declaratory language."
"Setup took about one day. We had some errors to understand in the beginning, but now everything is working good."
"The interface needs some work. It is not very user-friendly."
"It would be nice if they had a change management system offering. We built our own deployer application because the one built into webMethods couldn't enforce change management rules. Integration into a change management system, along with the version control system, would be a good offering; it's something that they're lacking."
"For code version control, you need to use some external software."
"The UI for the admin console is very old. It hasn't been updated for years and is pretty much the same one that we started with. This is something that could be refreshed and made more modern."
"The Software AG Designer could be more memory-efficient or CPU-efficient so that we can use it with middle-spec hardware."
"Forced migration from MessageBroker to Universal Messaging requires large scale reimplementation for JMS."
"Upgrades are complex. They typically take about five months from start to finish. There are many packages that plug into webMethods Integration Server, which is the central point for a vast majority of the transactions at my organization. Anytime we are upgrading that, there are complexities within each component that we must understand. That makes any upgrade very cumbersome and complicated. That has been my experience at this company. Because there are many different business units that we are touching, there are so many different components that we are touching. The amount of READMEs that you have to go through takes some time."
"We need more dashboards and reporting engines that can provide detailed information for management. In short, we need better analytics."
More webMethods Integration Server Pricing and Cost Advice →
AWS Step Functions is ranked 12th in Business Process Management (BPM) with 8 reviews while webMethods Integration Server is ranked 3rd in Enterprise Service Bus (ESB) with 60 reviews. AWS Step Functions is rated 7.8, while webMethods Integration Server is rated 8.0. The top reviewer of AWS Step Functions writes "Simplifies complex task automation and enhances development workflows while offering user-friendly interface, seamless scalability and efficient workflow orchestration". On the other hand, the top reviewer of webMethods Integration Server writes "Event-driven with lots of helpful formats, but minimal learning resources available". AWS Step Functions is most compared with Camunda, IBM BPM, Apache Airflow, Pega BPM and Oracle BPM, whereas webMethods Integration Server is most compared with IBM Integration Bus, webMethods.io Integration, Mule ESB, TIBCO BusinessWorks and Boomi AtomSphere Integration.
We monitor all Business Process Management (BPM) reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
