jawaidbazyar
New Member
- Reaction score
- 0
- Location
- Sarasota, FL
Hi, I would like to learn about you and your customers, and your thinking about "cloud" services.
Of course, the huge trend over the past 10 years has been virtualization, and more specifically, migration of what used to be local server / software services to 'the cloud' - of course IaaS - Amazon AWS, Google Cloud, Microsoft Azure, but also SaaS - Office 365, Google Apps, etc.
Lately I have been hearing a lot of talk about "data repatriation" where businesses want to bring control of their data back closer to home. For some larger business this means hosting data themselves again. But, since the value proposition of not running your own data center is still valid, I am wondering about whether some folks are thinking about leasing data center or perhaps dedicated servers, instead of bringing fully inhouse.
So, I'd like to start a hot and heavy discussion around this and the following questions:
First, do you think "cloud repatriation" is a real thing?
What % of your customers use cloud computing resources such as AWS, Azure, google, etc?
For a typical “cloud” customer, what are the drivers for them to put their workloads into a hyperscale cloud?
What OS’s do they run in the cloud? Windows / Linux / other
What does a typical cloud deployment look like? (e.g., 2 AD, 1 File Server, 1 Exchange, etc.)
To your mind, what are the pro’s and con’s of this approach?
What % of your customers use on-premise computing resources?
What are the drivers for them to keep workloads local?
What does a typical local deployment look like? (e.g., 2 AD, 1 File Server, 1 Exchange, etc.)
Do you use local hypervisors? If so what type (VMware, KVM, other)
To your mind, what are the pro’s and con’s of this approach?
Is there overlap? Do you have customers that are both hosting workloads in cloud and hosting locally?
What are some examples of this?
What are the reasons for splitting workloads in this way?
What do those deployments look like?
Of course, the huge trend over the past 10 years has been virtualization, and more specifically, migration of what used to be local server / software services to 'the cloud' - of course IaaS - Amazon AWS, Google Cloud, Microsoft Azure, but also SaaS - Office 365, Google Apps, etc.
Lately I have been hearing a lot of talk about "data repatriation" where businesses want to bring control of their data back closer to home. For some larger business this means hosting data themselves again. But, since the value proposition of not running your own data center is still valid, I am wondering about whether some folks are thinking about leasing data center or perhaps dedicated servers, instead of bringing fully inhouse.
So, I'd like to start a hot and heavy discussion around this and the following questions:
First, do you think "cloud repatriation" is a real thing?
What % of your customers use cloud computing resources such as AWS, Azure, google, etc?
For a typical “cloud” customer, what are the drivers for them to put their workloads into a hyperscale cloud?
What OS’s do they run in the cloud? Windows / Linux / other
What does a typical cloud deployment look like? (e.g., 2 AD, 1 File Server, 1 Exchange, etc.)
To your mind, what are the pro’s and con’s of this approach?
What % of your customers use on-premise computing resources?
What are the drivers for them to keep workloads local?
What does a typical local deployment look like? (e.g., 2 AD, 1 File Server, 1 Exchange, etc.)
Do you use local hypervisors? If so what type (VMware, KVM, other)
To your mind, what are the pro’s and con’s of this approach?
Is there overlap? Do you have customers that are both hosting workloads in cloud and hosting locally?
What are some examples of this?
What are the reasons for splitting workloads in this way?
What do those deployments look like?
