Share your experience using elastic.io

I am working on Informatica Intelligent Cloud Services currently.

As a consultant, I provide services to companies and clients using Informatica Intelligent Cloud Services.

The scalability of Informatica Intelligent Cloud Services is good. I can increase its size as and when required, and if any modifications are needed, it is easily adaptable. Monitoring is required but minimal, and there is a reduction in error rate.

The valuable features include ease of use and quick response time with Informatica Intelligent Cloud Services. The performance and response time are notably faster.

Previously we had Informatica PowerCenter on mainframe systems, but we have migrated everything to cloud systems. For cloud, we use Informatica Intelligent Cloud Services, which gives us better access, faster access, and improved performance.

Information about pricing and licensing of Informatica Intelligent Cloud Services is restricted to top-level management and project managers.

I have not used advanced data governance features inside Informatica Intelligent Cloud Services yet.

The system typically takes five to 10 minutes to respond.

Informatica Intelligent Cloud Services has a good user interface. However, when it comes to technical errors, we have to go through the logs. Error analysis becomes difficult as finding the exact location of the error in the logs is challenging. The log records could be better organized.

It is difficult for me to provide metrics regarding time saved or productivity gains using Informatica Intelligent Cloud Services features at this time.

I could not provide information regarding IICS's robust automation features for error-free data processing.

I have a meeting now regarding Informatica Intelligent Cloud Services.

I am working on Informatica Intelligent Cloud Services currently.

We access Informatica Intelligent Cloud Services via AWS. My company purchased it because we have projects for hundreds of people.

I could not evaluate other options or vendors before choosing Informatica Intelligent Cloud Services.

AI plays a significant role in optimizing our data workflows in Informatica Intelligent Cloud Services. It helps us fix errors, make modifications, and check dependencies. Since we are not aware of all dependencies once a project is deployed, AI assists us in identifying where changes will affect the system.

Neutral

We are dealing with billions of records of data. Quick responses matter significantly so we can fix any critical issues as soon as possible using Informatica Intelligent Cloud Services.

I do not have much information regarding the initial setup of Informatica Intelligent Cloud Services.

I could not evaluate other options or vendors before choosing Informatica Intelligent Cloud Services.

Maintenance and retrieval of records with Informatica Intelligent Cloud Services is easy. Time to retrieval is efficient, and we can access it from anywhere without requiring a particular mainframe location. It has good backup capabilities, allowing retrieval of accidentally deleted records through cloud backup servers.

I have minimal knowledge about its impact on the data integration process.

While there is a governance tool in Informatica Intelligent Cloud Services, I have not had the opportunity to work with it.

There is a governance tool in Informatica Intelligent Cloud Services, but I have not had the opportunity to work with it.

I have minimal knowledge about the impact on data integration process.

It is difficult to provide metrics regarding time saved or productivity gains using Informatica Intelligent Cloud Services features.

Information about pricing and licensing of Informatica Intelligent Cloud Services is restricted to top-level management and project managers.

AI plays a significant role in optimizing data workflows in Informatica Intelligent Cloud Services. It helps fix errors, make modifications, and check dependencies. Once a project is deployed, AI helps identify where changes will affect the system.

On a scale of 1-10, I rate Informatica Intelligent Cloud Services an 8.5.

The primary use case for Microsoft Azure Logic Apps in my system is mainly API Gateway; it serves as an interface between the external world and our entire ERP landscape. Any request which flows in our environment or goes outside from our environment touches the API Gateway. It handles transformation, request creation, transformation of the payloads, request payloads, and asynchronous flows, along with topics or message queues, which are the tools we utilize for asynchronous flows.

Assessing the ease of connecting disparate systems using Microsoft Azure Logic Apps connectors is simple because we have a Standard Operating Process. If we want to use Logic Apps, we just reserve the instances as per our requirement.

Even for Blob storage, we use tokenized endpoints that give us access to this storage account, making it secure. At API Gateway, we have policies that help us implement encryption and decryption. Request parameters are mapped automatically, converted to SOAP, XML, or JSON as needed in different formats.

We utilize its monitoring capabilities; Event Grids are used for logging events. Additionally, we have implemented a retry mechanism and are using Azure Monitor for end-to-end request tracing.

My experience with their pricing indicates that pricing is complicated to understand and costly. There should be some cost reduction.

Currently, I don't have any use case beyond what the readily available adapters provide for generating email or connecting with a backend database. Those facilities are readily available, and my requirement is just that much.

Our organization is utilizing that platform, and I am a customer.

I have been working with Microsoft Azure Logic Apps for more than three years.

I am not working with other IBM products; previously, I worked on IBM API Gateway. Instead, we switched to Azure Integration Services, AIS.

I am using it myself as I am a technical architect, so I have my team. We guide them to use the components as per the requirement, and then they develop the software or the integrations, whatever is needed.

I am working with an application infrastructure now, specifically Business Process Management. We don't have BPM, and we don't have any requirement for BPM currently.

My experience with Microsoft Azure products is great; they have many tools that support synchronous and asynchronous calls. We have a hybrid setup, with some things on cloud and the rest on our own infrastructure, so it helps us to implement the solutions as per our requirement.

I am mostly working with Microsoft Azure products such as API Gateway, Logic Apps, and then storage, specifically Blob storage. I use Logic Apps for collaboration through Azure DevOps, which helps us to automate the deployments.

At the infrastructure level, we typically monitor metrics using alerts for server monitoring. If a request is getting failed, we are monitoring based on error codes. We utilize error codes to write the logic for the retry mechanism.

We have a basis requirement for how Microsoft Azure Logic Apps integration with Office 365 has enhanced our business processes. For example, if some keys expire, we implement the Azure Key Vault. We use Logic Apps to trigger messages to regenerate the key or any public certificate close to expiring, which we have stored in Key Vault or other static parameters as per security guidelines. We configure those triggers or system-level alerts, and Logic Apps triggers the mail because it has a ready adapter for Office 365, ensuring the concerned L1 and L2 teams receive the necessary notifications to handle the errors.

On a scale of 1-10, I rate Microsoft Azure Logic Apps a seven out of ten.