Skip to main content

the real survivor

The three legged stool of business economics are something like [1] know your product [2] know your customer [3] know where the money is coming from. But there is also a silent fourth rule. Know your exit strategy or how to scale. If you know how to scale the business then you might have the next good and if not then just cash out and let someone else scale it. Most success stories result in one or two major successes and then a multitude of small ones. l refer to Shark Tank and The Profit.
Hidden in there are a few technical details that are typically missed by founders and technical leaders.
Certainly if you are building a compression algorithm, an electronic trading system, autonomous vehicle or ABS braking system, fly by wire; then writing your project in machine code, assembler or some variation of C or Ada then that makes the most sense. Compute cycles matter as long as you can count them.

But if you are building a business application like an accounting system, reporting, CRM, CMS, HRM then the intellectual property is in the workflow and not the algorithm. There is ABSOLUTELY no advantage to writing the business logic of the application in a native language like Go, C, C++, C#, Java, perl, python, ruby or any heavily compiled or interpreted language. If there are more than 100 to 150 APIs then its the wrong tool chain. By example I look at tcl, th1 and Lua. These languages are lightweight and require simple interpreters. In fact there is likely to be a basic interpreter for your favorite language which you can expand on.

Once the core system has been implemented then it can be bound to a GUI on the front end and "macros" on the back end. Both should be highly templated so that all systems can be manipulated easily. Furthermore migrating from domain to domain is just a matter implementing the basic services instead of the entire system. (at one in the process you will stave off the competition by implementing features so that the cost of entry is higher for the new competition. However, the velocity curve will always converge and so you'll need millions of lines of code to establish and hold a leadership position but then there is also LOC explosion that takes place when using templates and macros that the competition might not see.

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…