• Define Roadmap for Minimum Viable Cloud (MVC) and MVC+ (MVC +
Ongoing Roadmap)
• Define staffing plan for execution of MVC Build, Migration and EDW
operations
CAP Phase 3: Build
• Build MVC, including core elements of connectivity, access controls,
routing, auditing, logging, ACLs and automated deployment tools
• Create separate Dev, Test and Prod environments to match release and
test cycles
• Build database instances
• Set up staging environments for data replication, transformation
CAP Phase 4: Migrate
• Move data sets to the cloud EDW platform
• Implement ETL processes for ensuring data integrity between on-premise and cloud EDW platforms
• Migrate individual workloads and associated workflows, most commonly
moved in order of Dev, Test, Production workloads
• Retire on-premise supporting systems and infrastructure
• Migrate workflows to native cloud services where feasible
• Update all analytical models to leverage community supported languages like R or Python for easy execution in the cloud and portability
CAP Phase 5: Operate
• Implement operational monitoring and automated response to system
events
• Train operations staff to identify, debug and correct system events
• Identify operations team, existing or new, to operate and manage the
cloud EDW and supporting cloud services
Many organizations have organically built up EDW environments much larger
than traditional technologies can effectively accommodate. Organizations are
spending more and more every year for support, maintenance and to increase
capacity for varying workloads. The cloud provides unique capabilities to
accelerate many EDW workloads, while providing for better cost management
24 | THE DOPPLER | FALL 2016