Flowgear vs Microsoft Azure Logic Apps comparison

"Great for data flow."

"The Flowgear tool is helping us reduce the manual work that is done."

"Being able to seamlessly make changes to how one can do mapping visually without having to be a seasoned developer is great."

"Well-managed version control of workflows and the simplicity in promoting workflows through each environment has aided my team in developing workflows for various environments without the risk of losing development work."

"It has improved our integration with our data supplier."

"The no-code visual front end, along with pre-built samples, allows someone with very little technical ability to get an integration up and running."

"The solution has increased efficiency and productivity and saved us time and money."

"Easy to use and is able to integrate with other Azure-based environments."

"If there's something that isn't possible, you can write some code and call that code from a Logic App."

"I would rate my experience with the initial setup a nine out of ten, with ten being easy to set up."

"It's very easy to use, and it's blazing fast. The best thing about Logic Apps is actually its ability to create a solution in a matter of hours. It doesn't need any kind of provisioning, and you don't need any kind of hardware. You can create very small elements like these Logic Apps, and you can build a whole solution from those very simple and small elements. I also like that they are completely incorporated with your existing active directory. You can use user groups directly from the active directory inside Azure and access it from the Logic Apps. You don't need to do anything special, and you just have access. You can just check if the user is, for example, allowed to do some action. Normally it would take you some additional steps and some additional calls to check it. You have to come back to the active directory to make this possible. In Logic Apps, you just have it, and you can use it. I think that there's this concept of logging and recall to the Logic App. It shows you every single step, every single product, and the result it's returning to the next step. It also has an amazing debugging feature. You can rerun some calls and see if, after a correction of the Logic App, for example, you get the correct results. So, it's almost like it's alive. It's like you make a change, poof it, and it's in production, and it's working. The speed of the composition of the problem and creating a real solution for it is extremely fast with this solution. It's extremely fast in creation."

"It is a very stable solution."

"The workflow in Logic Apps enables integrating multiple applications."

"Logic Apps is good for helping us run our access on a cloud environment like Azure. It's much easier, more reliable, and better to maintain."

"If we are working with a service-oriented architecture, as an architect as a baseline, it supports us very well in terms of expandability, and the kind of robustness it brings, especially with its serverless nature is fabulous."

"The product needs to improve the self-help tools and samples."

"Currently, when designing and testing larger workflows, the sessions timeout and re-authentications are frequently required."

"The software itself needs to keep up with the daily demand to service all clients as the need arises."

"We would like to see more learning videos for beginners."

"The UI could be improved."

"The product would be nice if it could provide the deployment features in the lower packages."

"The initial setup was a bit complex as we were new."

"The documentation could be better. I think that's the only thing that was causing a normal level of problems. In terms of the documentation, it came from Cosmos DB and an additional product from Microsoft Azure."

"Microsoft Azure Logic Apps could have more customization options for connectors."

"Microsoft Azure Logic Apps is good for certain types of workloads, but it doesn't offer many customization options."

"The OpenAI components in Logic Apps could be more understandable."

"The business rules engine is still not fully developed, and it would be very helpful to see improvements here."

"Not all connectors are readily available, though. There are two types: managed connectors and app connectors. Some connectors require you to provide a username and password to connect to platforms like SharePoint or Salesforce. Due to security constraints, some users may prefer not to use these connectors. Instead, they might opt for the HTTP connector."

"It would be helpful if the vendor could provide more data connectors."

"In Microsoft Azure Logic Apps, we use Liquid templates, and I feel it can be improved as it does not support all the features that our company wants to use during any complex mapping when we might have to go for custom coding."

"The tool’s pricing could be better."

"It is a cost-efficient platform."

"I rate Microsoft Azure Logic Apps's pricing a seven out of ten."

"It's very cheap, but it comes with pluses and minuses. The positive thing is that it's very cheap, but on the other hand, it's extremely hard to tell how much it will cost. At the start of the project, it's almost impossible to tell how many times you will be calling some kind of Logic App function. You cannot state how much of the internet transfer you will use or how much data your will use."

"In my experience, Microsoft Azure Logic Apps is not a cheap solution."

"Its price depends on the number of transactions, storage capacity, etc., defining if the subscription will be monthly or weekly."

"The product pricing aligns well with the value and capabilities offered by Azure services."

"The pricing is okay. It's not highly priced. It's in the medium range."