A Discussion with Steppenwulf about Pivotal
I recently had an off-board discussion about Pivotal with Steppenwulf after he expressed some concerns in a board post. I thought I should post the discussion for all of you, as it seemed useful, and he concurred. This is all shortened and edited. Here’s the post that started it:
Steppenwulf sounds more doubtful
I’ve been been meaning to post about Kubernetes, which is getting really big traction across the board. Good that Pivotal got there in time, and is a leader in the space - but have to watch how the Kubernetes devel tools work out - RedHat is doing well, and though RedHat is growing a bit slow for this board, I may make a small investment, to make sure I keep an eye on it.
MongoDB is making a huge bet on Kubernetes (naturally, since it is a container that can hold a MongoDB), and also has a strong working partnership with RedHat - they are getting growth out of that relationship.
I don’t think VKE is a threat to Pivotal for a few reasons:
-
VKE is a public-cloud-only offering, and I can’t think of any reasonable use case why an enterprise company would be interested in a public-cloud-only Kubernetes environment - they could just use a cloud titan Kubernetes offering directly
-
The likely VMWare intention (just my guess) is that a major sales pipeline will be VKE rolled up into PKS as add-on offering, which simplifies multi-cloud deployment by PKS. It would make a lot of sense for VMWare to ask for some payback from Pivotal for the sales help VMWare provided to Pivotal in the past, and are still providing - and it makes sense for customers who want multi-public-cloud and it would probably be accretive for Pivotal.
Concerning Kubernetes, the picture is more confused. The base Pivotal product runs code. So thing you can’t put into a base Pivotal container is data. That is outside in some other managed system, and you point to it via configuration from your Pivotal container. Of course PKS manages Kubernetes containers so it can manage data containers that way. But Kubernetes is a bolt-on for Pivotal - they will need to dance fast to make sure they stay at the cutting edge.
Pivotal still has the advantage in that it is by far the best tool for improving developer productivity for cloud-native applications, and that it is truly vendor independent. But if enterprises feel they need to have at least some Kubernetes in order to host data work loads in the cloud, then other Kubernetes tool sets and new startups with newer containers will have a chance. I’m going to be keeping my eyes open
I asked him about it
Two months ago when you wrote up Pivotal you seemed to feel they had won the war. In this last post you seem to discuss them with much more ambivalence and doubt. Things must be evolving incredibly rapidly in the space. Do you still have faith/conviction in them?
He answered:
I still think they have won the war in code deployment on the cloud, but things can evolve quickly in tech. The fact that the base Pivotal product doesn’t support databases is a weakness I didn’t think much about. There are a few questions here:
-
Will Kubernetes continue its growth - it is also growing fast from a tiny base, so this could blow over as we get to enterprise.
-
Will Kubernetes become recognized as something that enterprise needs, in order to provide cloud neutral database work loads?
-
How will Pivotal do with PKS? Current Pivotal customers are using it - but will it be adopted by a big part of the Kubernetes crowd that aren’t currently Pivotal customers.
-
How will Pivotal play the data loads on the cloud? Remember that Pivotal has huge depth in data, and their team were major developers behind Hadoop (by the way, don’t believe the stories about the death of Hadoop - every major cloud data play involves a lot of Hadoop tech, HDFS is ubiquitous, and Spark is just another library that runs on Hadoop File System - this is just a pause as the Hadoop tools get easier for people to learn and use).
For a quick answer to your question - I haven’t changed my opinion of Pivotal at all for the next few years - it is the 5-10 years down the road where I’m looking at increased risk. My core competency is as a solutions architect, and what solutions architects think about, every minute, is risk vs reward. I’m always looking for risks, and evaluating it against my thesis and rewards. But if I actually thought the thesis had changed or broken, I would simply say SELL - and I don’t say that at all - I think Pivotal will be great for the next couple of years at least, but I want to watch Kubernetes closely.
I again asked about his ambivalence:
Thanks Steppenwulf, It now sounds to me as if you are on the positive-but-keeping-my-eyes-open side of ambivialent, having come down from super-enthusiatic about Pivotal. Correct me if I’m wrong.
He responded:
I’m still super-enthusiastic over the mid term - say 2 years. My question has always been when and how do they get to the midmarket? They can’t shoot up forever at the same rate unless they have a strategy for that. They have to start connecting with the mid market in say the next couple of years.
I had a blind spot - I didn’t think about a solution for a database. Pivotal needs a good solution for this. Logically this should not be too hard for them, but I don’t know how easy it would really be. Alternately, they can win in the Container market - no idea who is going to win in the enterprise container market yet, as it is tiny. Of course the smart thing would be to do both.
So, while their trajectory in the large enterprise market is set and they have no competitors, how their product development goes around data will help us to know if they can stay on top.
I hope this discussion is of help,
Saul