Share your experience using elastic.io

We develop and sell Microsoft Azure Logic Apps, so we are users of this solution.

The main use cases for Microsoft Azure Logic Apps are workflow management, some part of orchestration, and integration along with Service Bus.

The ROI with Microsoft Azure Logic Apps comes from the business process automation, and my customers have measured the value they get from the product.

The actions and Visual Designer in Microsoft Azure Logic Apps reduce the development time the most.

The most useful features of Microsoft Azure Logic Apps are the workflow part and the orchestration of services.

Scalability and reliability are benefits in Microsoft Azure Logic Apps.

The biggest advantage of Microsoft Azure Logic Apps is the workflow automation. Workflow automation and no-code, low-code development are its key benefits.

State management is the main challenge I have faced with Microsoft Azure Logic Apps during this period of time.

The issues I am facing with state management in Microsoft Azure Logic Apps arise because when you work with a state management tool elsewhere, such as a state machine, it is not easy to develop a state machine on Microsoft Azure Logic Apps. Though people say it can be developed, the state machine kind of requirement cannot be developed exactly with Microsoft Azure Logic Apps. It's an alternate tool. It's not the tool to be used for state management and state machines.

Better debugging capabilities within Microsoft Azure Logic Apps could be improved or additional features could be added.

Terraform template support should be available for Microsoft Azure Logic Apps.

For the last three to four years, I have been working with Microsoft Azure Logic Apps.

For a simple requirement regarding Microsoft Azure Logic Apps, deployment takes around three to four days. It majorly depends on the amount of complexity involved there.

Stability-wise, Microsoft Azure Logic Apps is not a problem. It's quite stable.

Premium support is available for Microsoft Azure Logic Apps. The normal support window doesn't help, as it requires premium support.

I would rate the support for Microsoft Azure Logic Apps a seven out of ten when using premium support.

Positive

The setup complexity for Microsoft Azure Logic Apps is medium.

On a scale from one to ten, where ten means a very easy setup, I would rate it a six for Microsoft Azure Logic Apps.

That depends significantly for Microsoft Azure Logic Apps. You can't generalize it because it depends on how many connectors you use, how many workflows you build, what scalability is required, and the amount of data to be ingested. There are many factors that affect the ROI.

Regarding the cost, I find Microsoft Azure Logic Apps to be reasonable; it is not expensive.

I recommend Microsoft Azure Logic Apps to those people who are planning to use it.

We are exploring AI-based applications with Microsoft Azure Logic Apps, though we have not implemented any currently.

I would recommend Microsoft Azure Logic Apps because it is a mature product. Though it has some limitations, it is stable and has evolved over the last 10 years. It's very much scalable and reliable.

In terms of industries, my customers include manufacturing, CPG, and retail when using Microsoft Azure Logic Apps.

The customers for Microsoft Azure Logic Apps are enterprise businesses.

On a scale of 1-10, this solution receives a rating of 7.

My customers' usual use cases for webMethods.io involve different billing and payment gateways. Many users are using it for business process engine.

In my experience with webMethods.io, the features or capabilities I have found most valuable include normal features such as caching, which is general and used in many applications such as Corba and TIBCO. Caching, data transformation, business rules, secure connectivity, and role-based rules are particularly beneficial.

I believe data transformation is exceptional in webMethods.io because they have an online database that can cache the database online. This is the most used benefit for the data transformation along with queuing, allowing quick file transfers in a very short period. This is the most important aspect to the client.

Secure connectivity in webMethods.io can be achieved by using SOAP and HTTPS, as you can use a secure protocol.

The secure protocol in webMethods.io is mandatory, as it protects all transactions and calls coming in or going out, especially when built with the methods API Gateway from companies such as IBM or Software AG. Both can secure the incoming connections to your network and provide flexibility to connect and integrate with all kinds of protocols and API gateways from other organizations.

My impression of webMethods.io's drag-and-drop interface to design workflows is actually amazing. It makes life easier for developers and end users who are using webMethods.io to change the rules and build any integration touchpoint from scratch without needing to write any single line of code—all done by dragging and dropping the components.

webMethods.io lacks advanced monitoring and analytics capabilities, so my customers need to use something additional.

Regarding the aspect of monitoring and analytics in webMethods.io, I wouldn't say it needs improvement; it was made for webMethods.io components, processes, and integration points. However, it cannot integrate with external services such as Apigee from Google for monitoring those web services in webMethods.io. You can monitor the calls between you and Apigee, but not the other calls to Apigee. Other platforms exist solely for these purposes, providing overall monitoring of applications and processes used by NOC departments.

In terms of areas in webMethods.io I would want to see improved in future releases, I think mainly the performance would be a focus, but the features already cover most if not all needs of integration. I've noticed components made to integrate with SAP and Oracle, but new applications in the market, such as ServiceNow, are booming. It would be good to have a separate component to cover integration and functionality for ServiceNow. Another enhancement would be in OCR; currently, there is a huge demand for OCR capabilities. It would be perfect if webMethods.io had a built-in component for OCR, as this would be tested and allow customers to use it better than a third-party OCR application. Having such a feature is essentially basic in modern applications.

I have been working with webMethods.io for seven years, since 2018.

In terms of stability, I find webMethods.io to be very stable. We provide support to our clients, and the minimum calls I receive are for webMethods.io; it's very stable.

Regarding scalability, I feel it's very scalable with normal procedures. Whenever more resources are needed, they become available automatically without any human interference. This makes scalability very automatic and easy.

I have not communicated with the technical support of webMethods.io or IBM support.

Neutral

The initial setup process of webMethods.io is simple and not complex.

Regarding the pricing and licensing of webMethods.io, I don't think it's expensive when compared with the features, but clients now see some budget differences because it previously belonged to Software AG, and now it's moved to IBM. The client feels this difference, and now it's slightly higher than the expected budget they planned for the last years.

I don't have any technical experience with this technical solution as I'm working in the sales domain. I'm selling webMethods.io and other solutions, but I don't have hands-on experience.

These features in webMethods.io are valuable to the customer; everyone needs it now.

I don't have a perfect answer regarding webMethods.io's support for hybrid deployments because I don't have technical experience in this part.

Most of my customers actually have their own applications for monitoring all the applications and back-end processes, but some have used webMethods.io and found it fine, even with the monitoring tool. However, the operation team usually monitors all applications together, so they prefer a unified application to gather all processes in one dashboard. From the practice I've seen with my customers, webMethods.io is one of the best applications for dashboarding, monitoring tools, and alert components; building alerts is very easy in webMethods.io.

If I were to rate the pricing of webMethods.io on a scale from one to ten, where one is cheap and ten is expensive, I would give it a five.

On a scale of one to ten, where one would be the worst product and ten the best, I rate webMethods.io a ten because it's very good and stable.