HashiCorp’s multi-product strategy
foundationinc.co
HashiCorp’s multi-product strategy
1–10 of 91 posts
Re: HashiCorp’s multi-product strategy
#2Anything to show growth. While I appreciate and understand having a vision, I'd have loved some of these products to just be as it is. With solid feature and we'll maintained. Alas that probably motivates no one and definitely not wall street
Re: HashiCorp’s multi-product strategy
#3Article is locked to members but the part that isn't doesn't convince me much.
Re: HashiCorp’s multi-product strategy
#4Although there's a paywall towards the bottom (is it 25%, 60%, 90% through the article, who can tell?), the above-the-fold resonates and is a reasonable narrative about HashiCorp's success. Certainly HashiCorp shines in the UX department.
That said, I think there's a another angle: HashiCorp is provider agnostic. HashiCorp tooling naturally lends itself to a multi-cloud strategy because they aren't owned by a cloud provider. Current requirements aside, coupling your business to the whims of Amazon, Google or Microsoft is always a risk. Even Kubernetes, the closest thing to an orchestration standard at scale makes me nervous because Google's needs are not the needs of most businesses, and what happens when they decide to throw their weight around?
As long as HashiCorp remains independent, I think it will attract a lot engineering-focused businesses that want to control their own destiny. I hope they can resist the urge to chase the enterprise money dragon to its logical conclusion. We are all better off for having some smaller-scale competition to the cloud behemoths who will only care about developer experience as long as they have to.
Re: HashiCorp’s multi-product strategy
#5Although there's a paywall towards the bottom (is it 25%, 60%, 90% through the article, who can tell?), the above-the-fold resonates and is a reasonable narrative about HashiCorp's success. Certainly HashiCorp shines in the UX department. That said, I think there's a another angle: HashiCorp is provider agnostic. HashiCorp tooling naturally lends itself to a multi-cloud strategy because they aren't owned by a cloud p…
Kubernetes is managed by a foundation so less of a risk than a tool owned by one company.
Re: HashiCorp’s multi-product strategy
#6Although there's a paywall towards the bottom (is it 25%, 60%, 90% through the article, who can tell?), the above-the-fold resonates and is a reasonable narrative about HashiCorp's success. Certainly HashiCorp shines in the UX department. That said, I think there's a another angle: HashiCorp is provider agnostic. HashiCorp tooling naturally lends itself to a multi-cloud strategy because they aren't owned by a cloud p…
> Google's needs are not the needs of most businesses, and what happens when they decide to throw their weight around
Nothing. Because AWS has invested heavily in Kubernetes and they would just fork the whole ecosystem.
They've done it in the past with Elasticsearch, Spark etc.
Re: HashiCorp’s multi-product strategy
#7Although there's a paywall towards the bottom (is it 25%, 60%, 90% through the article, who can tell?), the above-the-fold resonates and is a reasonable narrative about HashiCorp's success. Certainly HashiCorp shines in the UX department. That said, I think there's a another angle: HashiCorp is provider agnostic. HashiCorp tooling naturally lends itself to a multi-cloud strategy because they aren't owned by a cloud p…
Kubernetes is managed by a foundation so less of a risk than a tool owned by one company.
[deleted]
Re: HashiCorp’s multi-product strategy
#8Although there's a paywall towards the bottom (is it 25%, 60%, 90% through the article, who can tell?), the above-the-fold resonates and is a reasonable narrative about HashiCorp's success. Certainly HashiCorp shines in the UX department. That said, I think there's a another angle: HashiCorp is provider agnostic. HashiCorp tooling naturally lends itself to a multi-cloud strategy because they aren't owned by a cloud p…
Kubernetes is managed by a foundation so less of a risk than a tool owned by one company.
I think one way in which it plays out opposite to this is that Kubernetes, among companies I’ve talked to, is being deployed as EKS or GKE with cloud provider specific extensions/integrations while Nomad is much much easier to self manage on top of bare VMs. Even being owned by a single company, there is something about being to self host that feels more “free”.
Obviously this could make a 180 easily because of how much control HashiCorp has, but, thus far, they have been pretty good stewards.
Re: HashiCorp’s multi-product strategy
#9> There’s company-wide alignment on delivering the best user experience possible. That means sales, marketing, product engineering, product design, and customer success all channel their efforts into creating a product that provides an unparalleled UX. Product development puts all departments on the same wavelength in terms of the end goal.
Who the fuck are they talking about? Clearly not HashiCorp. The most popular tool in HashiCorp's ecosystem that wasn't written by them was written by a consulting firm who hated HashiCorp's UX. Hashi is like Amazon: shitty UX, but features that capture a market early, and so they remain a dominant player despite shitty UX and unnecessary overcomplicated bullshit.
There are only two things that you need to succeed with open source. 1) solve a problem nobody else has solved yet and drive massive adoption. 2) make it so that eventually people realize they can't get any farther without paying for enterprise features, and their lock-in and over-confidence from the free product will make them convince their bosses to pay you.
Re: HashiCorp’s multi-product strategy
#10> There’s company-wide alignment on delivering the best user experience possible. That means sales, marketing, product engineering, product design, and customer success all channel their efforts into creating a product that provides an unparalleled UX. Product development puts all departments on the same wavelength in terms of the end goal. Who the fuck are they talking about? Clearly not HashiCorp. The most popular…
> The most popular tool in HashiCorp's ecosystem that wasn't written by them was written by a consulting firm who hated HashiCorp's UX
Which tool is that?
On a related note, Vault has a really excellent API. A joy.