Skip to main content

Why enterprises and the super-rich get discounts

I was sitting at my desk writing a letter to the CEO at CoreOS. In chaotic fashion I was outlining how CoreOS might lose the container war and I outlined my reasons. I also described what I thought was a potential winning strategy given my experiences and perspective of history.

One recommendation I made was that CoreOS should have a lower cost of entry for developers, consultants and startups. And in the same recommendation I suggested that the enterprises should be subsidizing the startup and not the other way around. And lastly I was starting to outline what I thought were the 3 major layers and their offering.

What I wrote,

  • startup
  • establish
  • enterprise
what I read,
  • poor
  • middle-class
  • rich
I do not pretend to understand the sales, marketing or economic justification for why business' give deep discounts to enterprise customers. Once you have an enterprise customer they usually stick around a while. If you have a sticky technology they are not really going to leave for a very long while. And sometimes they'll just absorb you.

In my case I'm trying to get some tech welfare from CoreOS. Their product is good but the competition could put them out of business as Docker is truly the largest panamax container company (not to be confused with the real either thing). The CoreOS security model tells a chain of ownership story that might actually make banking, financial services, and every day computing safe... if the price is right.

-----

In my naive way, the reason that the poor and rich are subsidized by the middle-class is because of the physics. So long as the middle-class is the largest part of the population they will represent financial momentum. The rich and poor are volatile or transient as people enter and exit the middle-class.

Well that was a fun idea and it seems I was wrong and while that might have been how things were... they are not how things are. Reading this article it seems that the rich are now a larger percentage of the population and possibly getting larger. The rich now have the momentum and must subsidize the rest of us.

Popular posts from this blog

Prometheus vs Bosun

In conclusion... while Bosun(B) is still not the ideal monitoring system neither is Prometheus(P).

TL;DR;

I am running Bosun in a Docker container hosted on CoreOS. Fleet service/unit files keep it running. However in once case I have experienced at least one severe crash as a result of a disk full condition. That it is implemented as part golang, java and python is an annoyance. The MIT license is about the only good thing.

I am trying to integrate Prometheus into my pipeline but losing steam fast. The Prometheus design seems to desire that you integrate your own cache inside your application and then allow the server to scrape the data, however, if the interval between scrapes is shorter than the longest transient session of your application then you need a gateway. A place to shuttle your data that will be a little more persistent.

(1) storing the data in my application might get me started more quickly
(2) getting the server to pull the data might be more secure
(3) using a push g…

Entry level cost for CoreOS+Tectonic

CoreOS and Tectonic start their pricing at 10 servers. Managed CoreOS starts at $1000 per month for those first 10 servers and Tectonic is $5000 for the same 10 servers. Annualized that is $85K or at least one employee depending on your market. As a single employee company I'd rather hire the employee. Specially since I only have 3 servers.

The pricing is biased toward the largest servers with the largest capacities; my dual core 32GB i5 IntelNuc can never be mistaken for a 96-CPU dual or quad core DELL

If CoreOS does not figure out a different barrier of entry they are going to follow the Borland path to obscurity.

Weave vs Flannel

While Weave and Flannel have some features in common weave includes DNS for service discovery and a wrapper process for capturing that info. In order to get some parity you'd need to add a DNS service like SkyDNS and then write your own script to weave the two together.
In Weave your fleet file might have some of this:
[Service] . . . ExecStartPre=/opt/bin/weave run --net=host --name bob ncx/bob ExecStart=/usr/bin/docker attach bob
In sky + flannel it might look like:
[Service] . . . ExecStartPre=docker run -d --net=host --name bob ncx/bob ExecStartPre=etcdctl set /skydns/local/ncx/bob '{"host":"`docker inspect --format '{{ .NetworkSettings.IPAddress }}' bob`","port":8080}' ExecStart=/usr/bin/docker attach bob
I'd like it to look like this:
[Service] . . . ExecStartPre=skyrun --net=host --name bob ncx/bob ExecStart=/usr/bin/docker attach bob
That's the intent anyway. I'm not sure the exact commands will work and that's partly why we…