Database Reference
In-Depth Information
their data but don't have the capability to host their own Hadoop solution.
This scenario may happen for a couple of reasons. First, they might not have
the required capital to set up a decent-sized Hadoop cluster. Second, they
might not have the staff to do it. This may be especially true if executive
management hasn't yet fully come on board with the project.
The game has changed, and you are working through a real paradigm shift.
Your architectures will be much more complex in the short term as you
struggle to handle an ever-increasing amount of data and analytics you need
to apply to that data.
Ongoing Data Integration with Cloud and On-premise
Solutions
When developing a hybrid solution, data movement becomes an important
consideration. You will be tasked with moving data to and from the cloud.
You will need to develop a solution such that you can move that data
efficiently to either populate a solution in the cloud with data or to bring
data from the cloud to your on-premise environment. You will have three
main considerations:
1. What tool to use to move the data to and from the cloud
2. What compression codec to use
3. Whether a hybrid approach is actually the right approach (that is,
whether you should look at going all cloud or all on-premise)
You can use a number of tools to move data between your on-premise
solution and the cloud. The recommended approach is to use the data
movement tools that Microsoft has built right in to the Azure HDInsight
PowerShell Scripts. Using PowerShell may be the most straightforward way
of moving data from your on-premise environment to Windows Azure blob
storage. The first thing you need to do is install Windows Azure PowerShell
and then Windows Azure HDInsight PowerShell.
