This massive growth in scale has required an evolution in practices and organization to achieve success. Most of what technologists are aware of in this regard is labeled “DevOps,” but there is more nuance to it than that. The way infrastructure capacity is allocated becomes decoupled from specific hardware, so the infrastructure team has to adapt new tools. The way databases and message busses, among other things, are operated and made available to applications has become more “self-service”, and thus those teams have to see themselves as service providers rather than as infrastructure teams.
“There are a million solutions out there to your technical problems, but what we wanted was to solve the people and process problems,”
“It depends on Pivotal. If they add a common pattern in the future for deployment with Istio and Envoy through a cluster and platform-agnostic service mesh, then, yes, we will combine them,” said another senior engineer at the carrier.
A round-up of the news and some context around Microsoft burrowing down further into Kubernetes-land by acquiring Deis:
The deal & market
- Microsoft: “Deis gives developers the means to vastly improve application agility, efficiency and reliability through their Kubernetes container management technologies…. We expect Deis’ technology to make it even easier for customers to work with our existing container portfolio including Linux and Windows Server Containers, Hyper-V Containers and Azure Container Service, no matter what tools they choose to use.”
- Deis: “We look forward to making Azure the best place to run containerized workloads.”
- Deis is/was part of EngineYard, right? – Notable that EngineYard (on April 10th, 2017, day of announcement) doesn’t mention it on their blog, or press release list. And that Deis and Microsoft don’t really either. See 451’s Jay Lyman’s coverage of that deal in 2015.
- No deal-size was disclosed, of course, but Deis was small and I’m guessing it didn’t fit into EngineYard’s overall strategy, or what (little?) cash they got was a nice to have versus synergies of keeping Deis.
- Containers are rising in usage, as 451’s Donnie said: “Our latest data says production use of containers has doubled from 10.2% to 22.5% of orgs between Q1 and Q3 2015. Amazing.”
- 451’s January 2016 container market TAMs and forecast:
The technology: not so much PaaS anymore, but Kubernetes management
- Jan 2016 diagram of the Deis stack, above – so, pretty much a “cloud platform” competitor. Compare to Pivotal’s most recent snazzy-burger.
- “Creator at CTO at Deis”: “Best to think of Deis as a Kubernetes company. We are much more than the PaaS solution many folks know us for.”
- CNCF exec director: “their Workflow product (also open source), is basically the smallest piece of software that lets you run Heroku buildpacks on top of Kubernetes. So, you can get a 12-factor PaaS workflow, and still have the full Kubernetes API underneath if and when you need it.”
Microsoft likes Kubernetes
- Seems like Microsoft has gone all k8-crazy. So this is adding k8 support and some cloud-native services/middleware (package mgmt, routing, etc.) to Azure?
- Back in July of 2016, Microsoft hired a k8 big-wheel (and other, “small wheels,” I’d assume), so they’re obviously into the thing…or at least the thinking behind the think. This leave, once again, Amazon as the last major cloud hold-out on k8.
- That said, I think Microsoft’s new thing is to like everything that layers on-top, below, or around them. As long as you’re in every deal, you make a lot of money even if you’re not all of every deal. It’s pretty hard, now, of course, to compete with the big clouds.
- Or, put another way: “Satya is like the Pope Francis of software,” says Alex Polvi, founder and CEO of CoreOS, a company that plays in the same area as Deis. “He took this old institution and made it cool again.”