The only room for improvement for IDMC is the releases that they are committing. They need to be more transparent on the features that they are having versus not having. What I have seen is that in the readme document, they mention a capability is there, and once we introduce those things with our client, they always show up saying these are the limitations. During the release notes itself, they should mention the limitations of those new changes so that we are not in a bad situation in front of clients.The additional features I am expecting from IDMC in the future relate to cloud-native capabilities. Although they say that they are in a multi-tenant environment, the problem we have observed for a client in the tobacco industry using Microsoft is that they are having less support in terms of Microsoft versus Azure. GCP was very weak at the time when we were talking to them, and they said they will be introducing that, but I am not certain when they will do so.
I would say it can be a little bit easier to do the configurations because there are a certain number of points where we have to configure the endpoints and the plugins, and what kind of config it would be using. If it would be a little bit similar to on-premises where we do not have to put 10,000 different small things at 10 different places, then it would be a great tool to use. When it comes to integration, there are a certain number of places where we have to put twice those configurations to run them. Sometimes these are being missed and that is not the first thing you check because it has been assumed that the developer has done it. At the end of the day, if we are not able to find it in the first 30 minutes, then we always go into those areas, the plugins where it has to run, the environment variables and everything. Once that is sorted, then we do something else. The first 30 minutes is always spent going into the mapping if it is not running or anything. Then we go to environment variables. That is a little bit an overhead on the developer side. However, other than that, it is a good tool. It would be much easier if few environment variables are straightforward so that once configured, we do not have to configure them for every integration workflow. They should be global environment variables where we can put those tokens into them, config files into them, and that can be utilized by every single workflow which we create.
AWS Marketplace is a digital catalog that hosts thousands of software listings from independent software vendors. Businesses can find, test, buy, and deploy software in one place, easing the deployment process.AWS Marketplace offers a vast range of third-party software and services for cloud-based enterprises, observable in its streamlined procurement cycle. It delivers extensive options for integration, deployment, and management of applications on the AWS cloud, optimizing agility and...
The only room for improvement for IDMC is the releases that they are committing. They need to be more transparent on the features that they are having versus not having. What I have seen is that in the readme document, they mention a capability is there, and once we introduce those things with our client, they always show up saying these are the limitations. During the release notes itself, they should mention the limitations of those new changes so that we are not in a bad situation in front of clients.The additional features I am expecting from IDMC in the future relate to cloud-native capabilities. Although they say that they are in a multi-tenant environment, the problem we have observed for a client in the tobacco industry using Microsoft is that they are having less support in terms of Microsoft versus Azure. GCP was very weak at the time when we were talking to them, and they said they will be introducing that, but I am not certain when they will do so.
I would say it can be a little bit easier to do the configurations because there are a certain number of points where we have to configure the endpoints and the plugins, and what kind of config it would be using. If it would be a little bit similar to on-premises where we do not have to put 10,000 different small things at 10 different places, then it would be a great tool to use. When it comes to integration, there are a certain number of places where we have to put twice those configurations to run them. Sometimes these are being missed and that is not the first thing you check because it has been assumed that the developer has done it. At the end of the day, if we are not able to find it in the first 30 minutes, then we always go into those areas, the plugins where it has to run, the environment variables and everything. Once that is sorted, then we do something else. The first 30 minutes is always spent going into the mapping if it is not running or anything. Then we go to environment variables. That is a little bit an overhead on the developer side. However, other than that, it is a good tool. It would be much easier if few environment variables are straightforward so that once configured, we do not have to configure them for every integration workflow. They should be global environment variables where we can put those tokens into them, config files into them, and that can be utilized by every single workflow which we create.