“It’s 2019 so apparently everyone has a service mesh. Istio has been the most hyped – it has solid corporate backing from IBM, Google, Pivotal and SAP. These companies now need to do a better job of nailing use cases.”
HashiConf EU 2019: The Service Mesh push and Progressive Delivery
While many organizations have extensive on and off premise infrastructure investments, comparatively few of them are sophisticated in the way that those environments are tied to each other. If expectations are scaled back to the more realistic “multi-cloud” – the idea that an organization may have investments in more than one environment – the relevance and importance of OpenShift becomes more clear.
This is clever to point out that enterprises have enough trouble integrating their existing, on-premise stuff, let along the complexity and newness of tying together public and private cloud.
Original source: Big Blue Puts on a Red Hat: IBM Acquires Red Hat
“VMware’s ability to strategically partner to respond to shifting market forces is an impressive competency that should not be underestimated.”
Original source: Impressions from VMworld
“Progressive Delivery” – wrapping analyst-think and a sprinkle of business operations around rolling deploys.
Original source: Towards Progressive Delivery
“Docker is focusing on enterprise buyers and legacy workloads.”
Original source: Thoughts on DockerCon 2018
“Kubernetes has in fact already lost the war to serverless.”
All the cool kids are leap-frogging their thurt leadership.
Original source: Kubernetes won – so now what?
A fantastic, quick overview for understanding all those finance numbers and sheets.
Original source: Five Minute Finance
“In modern software development organizations, however, what gets used in development and testing environments has a habit of showing up in production. This was the opportunity that Kubernetes was built to take advantage of. It provided developers with a means – an open source means, naturally – of taking the containers they were so enamored of and running them in production environments, but without having to make determinations such as which containers run on which hardware. In its initial incarnation, this was the simple, basic job that Kubernetes was hired for.”
Original source: The Kubernetes Lesson
‘James Governor, Analyst at RedMonk said: “Brexit will be the biggest systemic shock to British business in the more than 70 years. The scale of change will require an unprecedented investment in IT, with in-house application development becoming more important than ever to deal with complexity.”’
Original source: Will UK lose global business and tech leader status post-Brexit?
Paying premium bucks to hire influencers for the big cloud migration wars.
Source: What is Microsoft Doing?
Turns out of course it’s not just Developer Time To Suck that is shrinking. Operations is heading the same way. Folks at Pivotal are saying that operating systems don’t matter, as we’ve moved further up the stack. Cloud Native is a proxy for saying much the same thing. But then, something is being written right now that will supplant Kubernetes. If we’re not running our own environments in house, operations disposability become increasingly realistic. Cattle not pets, for everything.
Good pointing out of needing some law and ethics to catch up to the Internet:
The Internet brought us hyperconnectedness, but we’re really not ready to cope. We don’t have institutions and firewalls in place to prevent abuse of the system. The law can’t keep up, and doesn’t have the teeth in place anyway.
Some highlights from a recent survey on container usage among 338 respondents to a Anchore/DevOps.com survey:
…approximately one third of the participants are running containers in production, with development coming in slightly higher.
Looking at the top five host operating systems across user roles we see Ubuntu having a particular strong lead among developers and architects.
Interestingly Mesos still features strongly with architects. Among developer communities we very rarely hear Mesos mentioned anymore. On the other hand we frequently encounter architects have invested in Mesos from the perspective of their big data environments and are looking at a common approach for their container strategy. That said, this entire market is extremely fluid at the moment.
…the combination of Jenkins and CloudBees (commercial Jenkins) approaching 50%.
Bluntly put [security] presents a barrier to adoption, and an opportunity for conservative organisations to hold off on adopting new technologies.
Our population breaks out with over 60% working in companies of greater than 100 people [and ~30% working in companies of greater than 5,000 people]…. With any data set of this nature, it is important to state that survey results strictly reflect the members of the DevOps.com community.
- As you’ll recall, 451 estimates that the container market will be $2.7bn in 2020.
- A 451 Research 1Q16 survey puts production use of containers at ~14%. It’s likely risen sense then, of course: maybe to around 18 to 20%?
- A 3Q2015 survey put “container orchestration” use at just ~9%. Presumably this is dev/test and production, all uses. And, again, you’d assume that it’s risen since then. The question would be: are people using containers in production without orchestration? That seems slightly crazy except for the simplest workloads, eh?
The wider Cloud Native ecosystem is, however, a very disparate and confused place. We anticipate a significant level of consolidation over the next twelve to eighteen months with some clear winners emerging. The emergence of several opinionated distributions of Kubernetes is hardly a surprise and this space will expand a little further before settling down.
There’s some proper, and surprisingly concise deal analysis over there:
While growth has come from the IoT, ARM’s resurgence in recent years – and Intel’s opposite trajectory – have been the result of the London company’s dominance in mobile devices. (In 2015, “45% of the ARM-based chips went into mobile devices.”) The so-called Wintel monopoly carried both of those parties to valuations that ARM never approached, but as mobile steadily eroded PC spend ARM’s low power designs found success on both of the most successful mobile platforms. Both Apple’s iOS devices and Android’s array of hardware are either exclusively or nearly so ARM-based.
Check out the rest!
Meanwhile, from John Abbott at 451 Research:
- ARM “generated less than $1.5bn in revenue last year and has only 3,300 employee”
- “SoftBank will pay 20.9x trailing revenue for ARM. That’s the first time any company has cracked the 20x mark in a $1bn-plus chip acquisition.”
- ARM “holds a 40% share in consumer goods, 30% in embedded intelligence, 15% in network infrastructure and 10% in automotive.”
- “Revenue reached $1.49bn in 2015, up 15% from the previous year, with a net profit of $360.7m.”
- Read more for his overall sentiment, which is basically: SoftBanks’ money and reach can fuel faster marketshare growth in these convert all the toasters to IoT grills times. checks out.