Share your experience using Bouvet Sesam

The main purpose of this tool is for file transfers related to our Python server.

The data integration and synchronization features in IICS improve the data handling processes.

I haven't had the chance to explore all the features in-depth since we've only been using them for a couple of months.  

I appreciate that it's a cloud-based solution. With a good internet connection, it works smoothly.

It also offers multiple features. 

There's definitely room for improvement in terms of user-friendliness.

One example is that you can't search for jobs directly by file name. You can only search by job name. So, if you want to find a job that works with a specific file, you have to go through each job individually to find the right one.

So, I'd like to see a faster search, one where I can search directly by file name.

Moreover, the support team could improve by adding things like file transfer status updates. Also, if someone modifies a job and then leaves the company, that shouldn't disrupt the job for active users. It would be better if the job continued to run smoothly regardless of who modified it.

I have been using it for seven to eight months. 

It is a pretty stable product. 

Scaling is easy. It's not overly complex. In our team, we have around 10 to 12 people using it. Additionally, there's a separate IT team dedicated to IICS with over 50 people. Other private projects likely use IICS as well.

We sometimes face challenges when implementing new features. In those cases, we contacted support, and they've been very helpful.

wWe're happy with the support team.

It is a cloud service. We use AWS and Azure Cloud. I'm not fully sure about the installation details, but I know we use AWS and potentially other cloud features as well.

If you have experience with similar tools or a general understanding of IT concepts, it's easier to grasp. Learning the features takes time, but with an IT background, you should be able to figure out the basics. 

We all encounter challenges sometimes and need to learn new things. Overall, it's not overly difficult or overly simple. It's manageable if you have the right mindset.

It's definitely a good tool, especially if you're using cloud services and an S3 bucket. It has many features to simplify your work and make your life easy. It's not overly difficult to learn, but proper training is essential to understand and make the most of all the features.

Overall, I would rate the solution an eight out of ten. 

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.

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.

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.

I have been using the product for a year. 

My company has 100 users. 

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

The tool's deployment is easy and manageable. 

The solution is worth its cost. 

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.

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.