Hacker News new | ask | show | jobs
by DanielDent 3798 days ago
We've actually been considering if we should turn our internal environment into a product and/or service-product mix.

We've got a mostly automated cloud-agnostic process for spinning up a multi-datacenter Mesos cluster which integrates nicely with a docker CI workflow.

I'm pretty sure it's quite valuable, though I'm also unclear what people would be willing to pay.

2 comments

> I'm pretty sure it's quite valuable, though I'm also unclear what people would be willing to pay.

Your solution probably works great for your needs, but this stuff is expensive to productize. See https://www.openshift.org/

Who I note basically decided to start from scratch because this docker thing happened. Cloud Foundry has had to do a lot of re-thinking too.

But my impression of openshift is that it's really a work in progress and that they haven't actually gotten it adequately productized yet.

Docker has gotten enough developer buy-in into containerization that I think it's fundamentally changed what it means to do infrastructure, be it PaaS or IaaS or whatever.

Probably an oversimplification on my part but it seems like OpenShift is nice enterprise friendly features sprinkled on top of Kubernetes. Which is no small thing, they've contributed quite a few patches to Kubernetes that are critical for a lot of enterprises. And a read/write GUI shouldn't be a hard requirement these days but a lot of big companies have this ingrained habit of treating IT like a commodity and subsequently hire people that are so uncomfortable with the CLI they're openly hostile to the idea of even touching it.

Then there's command and control. OpenShift seems to be more friendly to keeping things under someone's thumb. In an ideal world people would use Kubernetes the way Google uses Borg and devs would be trusted the way they are at Google. But between corporate fiefdoms and the aforementioned hiring practices many companies are still very far from that ideal.

IMHO, the problem is not only whether people will pay.

The problem is that this includes too many new tools that startups need to learn about, implement and maintain.

Most people, just reading "Mesos" "Marathon" or other in the space just tune out.

Agreed - and it's understandable why. The list of things that you need to understand before you get to work on your actual goal is way too long.

And there are a lot of nuances that make different tooling the right choice for different situations.

And the problem with trying to simply say "Do this" is what happens if your "do this" flow is tool X (similar to tool Y), but the CTO likes tool Y. Which isn't compatible with tool Z.

There are a nearly infinite number of ways to put together a decent development work flow.