At a recent developer conference for the popular Java web framework, Spring, the Pivotal SpringOne event in Austin, Texas, it hit home how important alignment around Kubernetes is in the cloud-native technology world.
The event host and open source project lead, Pivotal, was keen to quote from a recent JetBrains survey that said the two most popular offerings in the web framework category are Spring Boot (56%) and Spring MVC (43%), with the next most popular at only 6%. This article reflects Omdia’s experiences (wearing Kubernetes-tinted glasses) at the event. The reason for this is that to play in the cloud-native world today, you need to be part of the open source Kubernetes ecosystem. The pace of innovation is so rapid that it makes no sense to replicate your own Kubernetes equivalent, whether closed or open source, and to try to keep up with the efforts of a much larger community.
Kubernetes has emerged as a de facto standard in cloud-native computing and it has achieved this because it is open source, vendor-neutral, and its timing was perfect in solving the need to manage containers. Originated from Google, the open source project is today owned by the Cloud Native Computing Foundation (CNCF), a non-profit, vendor neutral organization in turn owned by the Linux Foundation. The Kubernetes ecosystem allows many players, from startups to Internet giants, to participate in cloud-native computing, fueling its growth and evolution.
VMware CEO Pat Gelsinger was invited on the opening keynote stage and talked about the company’s recent acquisition of Pivotal. VMware gave birth to Pivotal as an external partnership with Dell and EMC (now part of Dell), and bringing Pivotal inside VMware is a strategic move that is all about Kubernetes. VMware recently announced a Kubernetes-native vSphere (project Pacific), and project Tanzu, a build, run, and manage offering for cloud-native applications, again with Kubernetes at the center. This shows the pieces of VMware’s strategy falling into place, explaining why an even tighter embrace of Pivotal technology within the VMware stack makes a lot of sense.
All the public cloud players want to facilitate Kubernetes-based cloud-native applications, and with VMware calling itself the middleware for the cloud, it sees benefits in multiple ways. Pivotal gives it the grass roots developers, and its VM infrastructure stack attracts its enterprise customer base to the public cloud players that want to run these enterprise workloads.
The cloud is also a strategic play for Google, and it has played a benign role, supporting the open source community. It therefore came as a surprise that two important open source projects in the Kubernetes ecosystem, Knative and Istio, which were expected to join CNCF, will remain project managed by Google. While there is nothing wrong about this move by Google, given how much investment is flowing into the Kubernetes world, there will be suspicion that Google will steer these projects toward serving the Google Cloud better than its rival clouds. It remains to be seen whether Google can convince the community of the wisdom of its announcement to control these projects, or whether the community decides it is better to create a fork.
Moving to the cloud, and re-architecting applications to run optimally on the cloud is at the heart of digital transformation. Pivotal provides cloud technology, but to many of its target large enterprises, the re-architecting element is a huge undertaking. To help enable this, Pivotal has Pivotal Labs, the consulting body that helps enterprises master agile and DevOps and enter the brave new world of containers, microservices, and more. Large enterprises carry a huge amount of legacy (“heritage”) code, and to help transform this, Pivotal Labs has created agile techniques for large system modernization. This is a combination of methodologies and tools, such as the Boris method, a process for mapping architecture components (named after The Who song, Boris the Spider), and the SNAP (Snap Not Analysis Paralysis) method, which uses a Pivotal tool called App Analyzer that automatically analyzes code and provides complexity analytics, such as the degree of monolithic coupling across components. The Labs concept is a huge success that key rival IBM Red Hat has already emulated, but that is difficult to scale in large multinationals. The path taken by two customers, Dell and a large telco, is to create an internal version of Labs and have Pivotal train the trainers.
Pivotal arranged a customer panel to talk to analysts, Omdia’s two takeaways were first, tools do matter, while culture and people clearly matter, good tools (with first class automation) make a huge difference in easing digital transformation, and Pivotal Platform (formerly Pivotal Cloud Foundry) plays this role. Second, finding recruits with cloud-native skills is a persistent challenge. There is a large gap in our educational systems, and colleges are not turning out vocationally trained software engineers and so graduate recruits into high tech might have no idea what cloud-native computing is. It’s therefore not only a question of re-skilling IT staff whose comfort zone is waterfall, but it’s also necessary to train new recruits.
Finally, the event saw the announcement of the partnership with Microsoft on Azure Spring Cloud. In development since February 2019 and going live in early 2020, the arrangement gives developers a seamless and effortless move to the Azure public cloud via Spring. The platform takes care of all infrastructure concerns, providing “Spring Cloud as a Service”, and is a managed service by both companies. Platforms such as Spring carry significant enterprise workloads, and public cloud providers want large enterprises as customers, so expect to see interest from other public clouds.