Accelerating Innovation in the Analytic Ecosystem: Simplicity

Modern analytic ecosystems include capabilities that didn’t exist a few years ago. These new flexible capabilities increase complexity. Part of the increase in complexity can be attributed to characteristics related to data, performance, storage, compute, and connectivity. Increased desire for more analytics combined with increased data volumes, velocity and variety have increased the need for data stores with varying performance and cost characteristics. Computation needs for more complex enterprise wide analytics have forced the need for more scalable, powerful computing resources with variable performance and cost. 
 
Business users need compute resources more powerful than their desktops which leverage massively parallel computing, possibly GPU computing, with large amounts of memory and high bandwidth I/O. They need the ability to choose the right compute engine and data storage for their analytic problem. They may need these resources today, but possibly not tomorrow. Additionally, they need workloads executed on computing resources which are dynamically allocated at runtimes based on demand which could vary greatly.
 
The users need the ability to easily access and store potentially large volumes of data. To perform analytics, they need data from multiple systems in various formats residing in S3 compatible object stores or distributed file stores, e.g. HDFS. They need access to quality production data along with the ability to bring their own data. Quite often users need to combine data from multiple data stores and join it with data they’ve loaded into their discovery sandbox. Having multiple analysts manually moving data from multiple production platforms into discovery sandbox is time consuming, wastes resources, encourages data sprawl and lowers data quality over time via data drift. Users need to be able to query data easily and seamlessly without having to manually wrangle data from disparate data sources to execute analytics.
 
The IT team needs to manage analytic resources used in production and discovery environments. IT must ensure that production workloads meet SLAs, but also need to ensure that analytic discovery resources are available, accessible and secured. For IT, it is critical that IT resources provisioned for analytic sandboxes are sanctioned, flexible and well managed.

Business Needs:
 

• Access to storage and compute resources to support business analytics needs
• Simplified provisioning process to obtain resources for analytic exploration and innovation
• Easy access to data in multiple data stores via virtualization to reduce the need for data replication
• Simplified analytic entry point

IT Needs:
 

• Standardized provisioning of sanctioned resources for discovery analytics to ensure supportability and speed time to value
• Ensure production SLAs are being met
• Enabling virtualization capabilities to simplify data access and analytic processing over a high-speed fabric
• Optimizing and rationalizing resources for cost efficiencies
• Manage / monitor production & discovery resource usage

Recommendations:
 
Recommendations for enabling simplicity for compute, storage and connectivity:
 
IT Focused
 

• Provide an analytics discovery/innovation platform with adequate compute, storage and connectivity to support the analytic needs of the business. Leverage new technology such as object stores which provide very low-cost storage with reasonable data transfer rates at higher latencies which is acceptable for most analytics running against large data sets.
• Promote an environment which minimizes the friction of moving analytics from exploration into production.
  • Create analytic ops frameworks and processes which enable easily promotion of new data and analytics into production with the proper governance to ensure ongoing quality in the data and analytics.
  • Proactively work with the business on evaluating new tools and technologies which meet their needs, are approved and funded, and rationalized into the analytic ecosystem.
• Establish simple auto-provisioning capabilities for users to establish sandbox resources.
  • Instantiate sanctioned resources which are powerful enough to meet user’s analytic needs with enough monitoring to be efficiently managed.
  • Provide provisioning defaults by persona, but allow for exceptions.
• Provide a high-speed data fabric between data storage platforms which reduce data transfer latency and minimize the need for data replication.
• Establish data virtualization capabilities and policies which simplify access to data in multiple data stores. 
  • Automate the creation of foreign tables to support simple SQL based access to data across platforms.
• Balance IT needs of performance, flexibility and total-cost-of-ownership for the analytic ecosystem, with the business needs for discovery and innovation.
• Implement workload management capabilities which can ensure production can meet its SLAs while enabling discovery environments to directly access production data.

 
Business Focused
 

• Utilize IT sanctioned environments to minimize effort and time to move discovery analytics into production.
• Leverage IT provided auto-provisioning process to speed access to analytic environments.
• Leverage data virtualization to join data on-demand via SQL from multiple data stores instead of creating load jobs, minimizing data replication, improving data quality and maximizing speed to insight.
• Proactively work with IT on new technologies which address business gaps.
• Focus on time to insight vs performance while in discovery.

 
Simplicity enables users to quickly provision their own analytic sandboxes to focus on analytics for solving their business problems.  When IT provides the simple provision capabilities to the user community, it can ensure the resources can be supported, monitored and managed to provide visibility into the data being loaded and the analytics processes being executed. The users have great freedom of the various types of resources they can leverage, and IT has visibility of the resources allocated and being utilized. 

In the third and final article in this series we will discuss the importance of Accessibility.