5 ms·

I can see an an argument that kubernetes workloads should be on GCP for the same reasons MS workloads should be on Azure.

scarface74 7y ago
There is no special reason that MS workloads that should be on Azure. AWS is always bragging that they have twice as many Windows VMs as Azure. The only two features that I’m aware of on AWS that won’t work for Windows is lambda and Fargate. AWS SDKs, documentation and support for Windows/.Net Framework is excellent. I’m not making any technical arguments against Azure. I haven’t used it besides what is now “Azure Devops”. As far as Kubernetes. It’s inconsequential when a major corporation is considering which cloud provider to use. Most existing workloads on prem are not using k8s. That goes back to knowing how to meet the customers where they are and knowing how to do a “lift and shift” as phase 1.
- JamesSwift 7y ago
  I'm not saying they are technical arguments. I'm saying they are the same acceptable answers to "why did you choose (not AWS)". Because the platform I chose is also part of the foundation of the tech stack we run on.
  - scarface74 7y ago
    Kubernetes - which every cloud provider now offers as a managed service - might win you a few startups but won’t win you many major enterprise companies.
    - dodobirdlord 7y ago
      You'd probably be surprised. Kubernetes is a hot enough buzzword that even companies as bizarre as Chick-fil-A are getting on board, with a hilarious architecture. https://medium.com/@cfatechblog/bare-metal-k8s-clustering-at-chick-fil-a-scale-7b0607bd3541 https://medium.com/@cfatechblog/bare-metal-k8s-clustering-at... Edit: Way past the getting-on-board stage, apparently. It had slipped my mind that the article I linked is from 18 months ago and already described an extensive rollout.
      - sciurus 7y ago
        FYI I saw a presentation by the team at CFA after that blog post was written. They said the in-store K8s deployments were only running greenfield, non-production applications. I don't know if that's changed.
      - scarface74 7y ago
        That’s a great anecdote, but small fry when compared to all of the other F500 companies that MS and AWS are able to court by using their thousands of partners that are intimately familiar with enterprise on prem workloads and know how to slowly migrate customers. MS has decades of building relationships with large companies that it can leverage. If Google’s only proposition is that it’s cheaper, any AWS Solution Architect can negotiate lower prices from AWS if they want to secure a client that’s large enough.
    - pm90 7y ago
      How do you think major enterprise customers are formed? Also GCP already does have some large enterprise clients. Some of them have had a symbiotic relationship with them, working closely to create the features they need as they scale. That kind of treatment is hard to get with AWS where most enterprises would be small fry by comparison. There are also enterprises that don’t want to be on Amazons stuff for reasons.
      - scarface74 7y ago
        How many hot startups have become “major corporations” in the last 5 years. All you have to do is watch the thousand plus reinvent videos to know that AWS does work with many major companies. They also have an extensive partner network.
- basch 7y ago
  >MS workloads that should be on Azure. Microsoft is breaking apart what WAS Windows Server, into discrete managed services. Identity Services, File Services, etc. If you have a need for what was formerly Windows Server provided stuff, and youre rebuilding infrastructure, you would get a lot of compatibility from Azure. Then, as you need other compute and storage resources, youre building on top of a service contract you already have, instead of spreading your data all over the clouds.
  - scarface74 7y ago
    As is Amazon. They have hosted Active Directory and hosted Windows File Servers. Amazon is not crazy enough not to cater to Windows workloads when that’s what many enterprise companies are using.
    - basch 7y ago
      But amazon doesnt make Active Directory. Microsoft can continue to create new versions and new features that are released as a service, but not in the on prem component. You already see that in exchange, sharepoint, lync.

scarface74 7y ago

There is no special reason that MS workloads that should be on Azure. AWS is always bragging that they have twice as many Windows VMs as Azure. The only two features that I’m aware of on AWS that won’t work for Windows is lambda and Fargate. AWS SDKs, documentation and support for Windows/.Net Framework is excellent. I’m not making any technical arguments against Azure. I haven’t used it besides what is now “Azure Devops”. As far as Kubernetes. It’s inconsequential when a major corporation is considering which cloud provider to use. Most existing workloads on prem are not using k8s. That goes back to knowing how to meet the customers where they are and knowing how to do a “lift and shift” as phase 1.

JamesSwift 7y ago
I'm not saying they are technical arguments. I'm saying they are the same acceptable answers to "why did you choose (not AWS)". Because the platform I chose is also part of the foundation of the tech stack we run on.
- scarface74 7y ago
  Kubernetes - which every cloud provider now offers as a managed service - might win you a few startups but won’t win you many major enterprise companies.
  - dodobirdlord 7y ago
    You'd probably be surprised. Kubernetes is a hot enough buzzword that even companies as bizarre as Chick-fil-A are getting on board, with a hilarious architecture. https://medium.com/@cfatechblog/bare-metal-k8s-clustering-at-chick-fil-a-scale-7b0607bd3541 https://medium.com/@cfatechblog/bare-metal-k8s-clustering-at... Edit: Way past the getting-on-board stage, apparently. It had slipped my mind that the article I linked is from 18 months ago and already described an extensive rollout.
    - sciurus 7y ago
      FYI I saw a presentation by the team at CFA after that blog post was written. They said the in-store K8s deployments were only running greenfield, non-production applications. I don't know if that's changed.
    - scarface74 7y ago
      That’s a great anecdote, but small fry when compared to all of the other F500 companies that MS and AWS are able to court by using their thousands of partners that are intimately familiar with enterprise on prem workloads and know how to slowly migrate customers. MS has decades of building relationships with large companies that it can leverage. If Google’s only proposition is that it’s cheaper, any AWS Solution Architect can negotiate lower prices from AWS if they want to secure a client that’s large enough.
  - pm90 7y ago
    How do you think major enterprise customers are formed? Also GCP already does have some large enterprise clients. Some of them have had a symbiotic relationship with them, working closely to create the features they need as they scale. That kind of treatment is hard to get with AWS where most enterprises would be small fry by comparison. There are also enterprises that don’t want to be on Amazons stuff for reasons.
    - scarface74 7y ago
      How many hot startups have become “major corporations” in the last 5 years. All you have to do is watch the thousand plus reinvent videos to know that AWS does work with many major companies. They also have an extensive partner network.
basch 7y ago
>MS workloads that should be on Azure. Microsoft is breaking apart what WAS Windows Server, into discrete managed services. Identity Services, File Services, etc. If you have a need for what was formerly Windows Server provided stuff, and youre rebuilding infrastructure, you would get a lot of compatibility from Azure. Then, as you need other compute and storage resources, youre building on top of a service contract you already have, instead of spreading your data all over the clouds.
- scarface74 7y ago
  As is Amazon. They have hosted Active Directory and hosted Windows File Servers. Amazon is not crazy enough not to cater to Windows workloads when that’s what many enterprise companies are using.
  - basch 7y ago
    But amazon doesnt make Active Directory. Microsoft can continue to create new versions and new features that are released as a service, but not in the on prem component. You already see that in exchange, sharepoint, lync.