Share your experience using elastic.io

With Microsoft Azure Logic Apps, we can orchestrate and pull event-based triggers. We can use the solution to schedule a workflow based on any new record inserted into our database.

The solution's best feature is that it is compatible with the cloud and has many connectors and third-party adapters. You can connect it with almost every system.

We have lots of other systems. When we raised a complaint with Microsoft, they asked us not to use the solution for a particular purpose. We wanted to use Microsoft Azure Logic Apps, but we faced a timeout. We had a call with Microsoft regarding one of the issues. The support person with whom I was discussing was also not very comfortable with that question.

I have been using Microsoft Azure Logic Apps for the last one year.

We are working on the same technology in our company. Approximately 40 to 50 people on our team use Microsoft Azure Logic Apps.

The solution's customer support depends on the type of partner you are. If you are a gold partner, they will reply immediately. However, if you have a lower level of collaboration with Microsoft, they will take some time. The technical support team does fix issues, but they take time.

The initial setup of the solution would be a bit difficult if you are using CI/CD. CI/CD, container integration, and container deployment are one-time processes. Setting them up once makes the rest of the deployment easier. If you don't do it initially, you have to copy and paste, which will take time. I suggest you invest time in creating a CI/CD to avoid the later dependencies or consequences of not using CI/CD.

You will be charged too much if you are unaware of the solution's cost. Initially, when I was doing my development and POCs, one day, I forgot to close the connection or the artifact I created. The next morning, I learned that INR 40,000 had been deducted from my credit card.

Some companies use the solution for monetary benefits. Other companies upgrade their technology to compete with other technologies. In my current organization, everything is working fine, but they must also upgrade their technology. They were not saving money with the tool but had to upgrade themselves in technology.

You should be aware of the solution's configuration. You don't have to write any code, even for your basic work needs. However, you do have to configure some things and be aware of the triggers and actions. There is also a lot of help available on Google and YouTube to do it.

We have to write the code in such a manner that the next person who is using it or visiting that particular code should be aware. If you don't write properly what type of work you are doing inside a particular code, it'll be very difficult to identify what you have done. If I pick one particular action, the action should be very clear about what I'm doing in that action.

Otherwise, it will be very messy. If you use the default naming structure, it will be like one, two, or three variables. If you do not write the proper name of that variable, it'll be very difficult to identify what type of work you were doing inside that scope, function, or action.

Overall, I rate the solution a seven out of ten.

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.