As mentioned already 1st and foremost is data security whilst inflight and when at rest (cached). But not just technically but also the human processes around security such as data centre operations - think of SSAE16 for example.
Next up is execution location, depending on the data it maybe subject to data protection rules or contractual residency.
Once past the security/hosting/compliance/certification related questions, then need to think about capacity/throughput and latency. If your integration is part of a user experience you don't want the integration to flow through solutions quickly. That means you need rapid scaling to manage fluctuations in demand.
IT Consultant at a tech services company with 1,001-5,000 employees
Consultant
2017-04-04T11:05:59Z
Apr 4, 2017
In my opinion, the following steps need to be considered before we move on to integrate systems,
* What systems that need integration.
* The limitations of the software
* How will the solution affect the employees?
* Which vendor will support which applications?
* How much will it cost to integrate the applications and what will be the impact?
* How quickly can I go to market?
Answer: Maximum flexibility within cost constraints.
Whilst a cloud data integration platform with open standards is preferable for maximum digital growth, if cost is the prohibitive factor then any short term integration should have future flexibility applied to it.
Principal, Enterprise Architect at a tech services company with 1,001-5,000 employees
Consultant
2017-03-07T00:41:17Z
Mar 7, 2017
The Most important
1. Security (both cloud and connectivity to on prem)
2. If you are looking for volume data
a) performance (throughput)
3. availability %
4. frequency of updates
5. compliance
6. Enterprise connectivity support
7. cost
One aspect that is important is evaluating what kind of data you are willing to put on the Cloud, security and performance are still issues that must be considered. For performance you need to consider how is the data going to be consumed (once a day, real time ?) and the volume that needs to be available on an ongoing basis. I always recommend companies to keep some current data On-Premise and new non-sensitive data on the Cloud and start growing that way, a hybrid system seems to work the best. Plus if the internet goes down, you can still run your business with local systems.
What is cloud data integration? Cloud data integration refers to the process of integrating data used by disparate application programs between public or private clouds, or between on-premises and cloud-based systems.
The ability to ensure and enforce data quality.
Transparency and traceability via end to end data lineage.
Ability to automate acceptance and regression testing.
Operational supportability.
As mentioned already 1st and foremost is data security whilst inflight and when at rest (cached). But not just technically but also the human processes around security such as data centre operations - think of SSAE16 for example.
Next up is execution location, depending on the data it maybe subject to data protection rules or contractual residency.
Once past the security/hosting/compliance/certification related questions, then need to think about capacity/throughput and latency. If your integration is part of a user experience you don't want the integration to flow through solutions quickly. That means you need rapid scaling to manage fluctuations in demand.
After that it is connectivity & ease of delivery.
In my opinion, the following steps need to be considered before we move on to integrate systems,
* What systems that need integration.
* The limitations of the software
* How will the solution affect the employees?
* Which vendor will support which applications?
* How much will it cost to integrate the applications and what will be the impact?
* How quickly can I go to market?
Answer: Maximum flexibility within cost constraints.
Whilst a cloud data integration platform with open standards is preferable for maximum digital growth, if cost is the prohibitive factor then any short term integration should have future flexibility applied to it.
The Most important
1. Security (both cloud and connectivity to on prem)
2. If you are looking for volume data
a) performance (throughput)
3. availability %
4. frequency of updates
5. compliance
6. Enterprise connectivity support
7. cost
One aspect that is important is evaluating what kind of data you are willing to put on the Cloud, security and performance are still issues that must be considered. For performance you need to consider how is the data going to be consumed (once a day, real time ?) and the volume that needs to be available on an ongoing basis. I always recommend companies to keep some current data On-Premise and new non-sensitive data on the Cloud and start growing that way, a hybrid system seems to work the best. Plus if the internet goes down, you can still run your business with local systems.
compliance and data security