Share your experience using Cloudsnap

The easiest route - we'll conduct a 15 minute phone interview and write up the review for you.

Use our online form to submit your review. It's quick and you can post anonymously.

Your review helps others learn about this solution
The PeerSpot community is built upon trust and sharing with peers.
It's good for your career
In today's digital world, your review shows you have valuable expertise.
You can influence the market
Vendors read their reviews and make improvements based on your feedback.
Examples of the 84,000+ reviews on PeerSpot:

Srinidhi S - PeerSpot reviewer
Software Engineer at Shell
Real User
Has different connectors for workflow and comes with low-code feature
Pros and Cons
  • "The solution's most valuable feature is the no-code/low-code feature."
  • "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."

What is our primary use case?

Microsoft Azure Logic Apps' main use case is workflow. Depending on your needs, many available connectors allow you to configure it with different systems, whether on-premises or in the cloud. They start with a trigger and then execute steps one by one.  Just as we use features in Excel, the tool can manage different tasks and handle various data formats.

What is most valuable?

The solution's most valuable feature is the no-code/low-code feature. Due to certain restrictions, we might be unable to use some connectors, particularly if they involve sensitive information like usernames and credentials. In such cases, you could use the library. Then, you can deploy that function app to the same subscription and call it via Microsoft Azure Logic Apps.

What needs improvement?

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. However, tracking can be a bit challenging. In production, the run history might not be accessible due to security restrictions.

For how long have I used the solution?

I have been using the product for a year. 

What do I think about the scalability of the solution?

My company has 100 users. 

How are customer service and support?

The tool's support is helpful and does a great job. 

How was the initial setup?

The tool's deployment is easy and manageable. 

What was our ROI?

The solution is worth its cost. 

What's my experience with pricing, setup cost, and licensing?

The tool's cost can vary depending on your specific use case. Generally, it's considered cheaper, but the price depends on how much you use it and which features you need. Initially, there was a consumption-based pricing model, but now Microsoft offers a standard tier. Microsoft encourages users to migrate from the consumption model to the standard one by 2025. The pricing is a monthly fixed cost, depending on your usage needs.

What other advice do I have?

If you're trying Microsoft Azure Logic Apps for the first time, begin by learning its basics. Understand how to deploy and use it. Then, some practice projects should be done to see how it works in different situations. Finally, get hands-on experience through the Azure portal to feel more comfortable using it for real projects.

If you have a use case where you need to utilize an Azure function, you can directly call that function from within Microsoft Azure Logic Apps using a connector. This connector allows you to call the function with specific inputs and methods, such as Post or Get. Additionally, certain connectors available exclusively in Azure, like blob-related connectors, offer valuable resources for tasks such as editing or creating blobs. 

I rate the product a ten out of ten. 

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Microsoft Azure
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
Head of SOA Center of Excellence at a computer software company with 10,001+ employees
Consultant
Useful for API management and integration
Pros and Cons
  • "The tool is very capable and offers a high performance. The tool supports batch processing and ETL processing."
  • "The high price of the product is an area of concern where improvements are required."

What is our primary use case?

I use the solution in my company for API development and integration.

What is most valuable?

The most beneficial part of the product for API management tasks stems from the fact that it makes me capable of doing a lot of integrations and design patterns, including areas for regular integrations and ETL. The tool offers a very high performance and is very customizable, and my company didn't get into a complex task that we couldn't achieve with Mule Anypoint Platform. I am working with a very big organization where there are a lot of challenges, but till now, with the challenges my company has faced, we could face them in both areas, like management and API integration.

What needs improvement?

Anypoint Studio for developing integrations can be described as a moderate to complex process, and from an improvement perspective, it needs to be made easier.

Mule Anypoint Platform has developed a new development studio based on Visual Studio Code, but it is still in the beta stage, so my company hasn't used it yet. I hope in the future, it will be easier to use the tool because the current Anypoint Studio is based on scripts, which are quite heavy. My company hopes that in the future, with Visual Studio Code, the development studio would be easier to use.

The high price of the product is an area of concern where improvements are required.

For how long have I used the solution?

I have been using Mule Anypoint Platform for more than two years. I am an implementer, developer, and customer of the tool.

What do I think about the stability of the solution?

Stability-wise, I rate the solution a nine out of ten.

What do I think about the scalability of the solution?

It is a scalable solution. Scalability-wise, I rate the solution a ten out of ten.

My company's clients are usually enterprise-sized companies.

How are customer service and support?

I rate the technical support an eight or nine out of ten.

How would you rate customer service and support?

Positive

How was the initial setup?

I rate the product's initial setup phase a three on a scale of one to ten, where one is difficult, and ten is easy. The product's initial setup is difficult.

The solution is deployed on a private cloud.

The solution can be deployed in a few weeks.

What's my experience with pricing, setup cost, and licensing?

The product is expensive.

I rate the product price a nine on a scale of one to ten, where one is cheap, and ten is expensive. It is complex to figure out the average price of the product.

What other advice do I have?

Anypoint Platform is a part of MuleSoft, and it can be considered its main USP.

Deploying and managing APIs using Mule Anypoint Platform is complex, but I really like the tool. It is a very capable solution. My company put me in charge of comparing many tools in the market to find a hybrid integration solution, after which we found that Mule Anypoint Platform was the best hybrid tool, both in API management and integration. My company is pleased with the tool despite it being a complex and complicated product since it is a very capable solution. You can do everything with it.

The ease of use of the Anypoint Studio for developing integrations can be described as a moderate to complex process. It is not an easy process.

My company did not use the product's cloud services but instead opted for our own private cloud, which supports scalability.

I recommend the product to those who plan to use it, especially enterprise-sized businesses, as it can be used as a strategic integration solution that can support various use cases of integration in the present and the future. The tool is very capable and offers a high performance. The tool supports batch processing and ETL processing. As a hybrid solution, Mule Anypoint Platform is the best. The tool offers central management, and it can manage both on-premises and cloud solutions. I think it's the best tool in the market today, specifically since it offers central management capabilities. It is a good solution for enterprise-sized businesses. My company did a really thorough comparison of other tools against Mule Anypoint Platform. Mule Anypoint Platform is a complex and expensive tool, but it allows you to meet all of your integration needs, along with design patterns and security.

I rate the overall tool a nine out of ten.

Which deployment model are you using for this solution?

Private Cloud
Disclosure: My company has a business relationship with this vendor other than being a customer: Implementer
Flag as inappropriate