The Doppler Quarterly Fall 2016 - Page 23

take advantage of best practices around sending only differential changes, as well as maximizing data compression before sending. Developer Experience – Cloud based EDWs provide unique flexibility and capabilities that are not available in on-premise solutions. This can be challenging for developers who need to keep up with regularly released new features and learn new methods for service utilization. Cloud EDW projects should include training and enablement efforts, to ensure developers have access to examples, curriculum and resources when adopting cloud EDW. Figure 2: Cloud EDW Integration While any IT service migration is risky, an EDW adds additional risk because of the critical nature of the system in managing the core business functions of a company. When moving to a cloud EDW, there are several key areas that should be assessed, evaluated and planned for prior to migration: Use of proprietary features in on-premise EDW implementation – All uses of proprietary features should be evaluated prior to migration to determine how best to provide similar functionality in the cloud. Developer Experience & Data Access – Developers need to be provided a similar experience with their cloud based EDW as they’ve been accustomed to in the data center. This ensures their productivity is not impacted when deploying new workloads in the cloud, or working on integration activities between the platforms. Query Cost – Some cloud services charge based on the amount of data queried. This model can provide advantages with many workloads, but needs to be communicated to all developers to ensure they are efficient at all tasks and understand the cost of adding new reporting capabilities. FALL 2016 | THE DOPPLER | 21