Skip to main content

scripting in golang

There are a number of choices when it comes to scripting in golang. The first and most obvious is the template library. The point of the template library is to produce a document as a resultset and while data goes in and is partially mutable inside the template there is nothing other than the document coming out. Therefore as a general purpose scripting language it's not that effective.

When golang was younger there were a number of places where people could get reliable vanilla packages. A vanilla package is a package that has no dependencies of it's own other than the packages supplied with golang. This is a very big problem for nodejs because there is a lot of nested dependencies.

All of that mess aside I have many use-cases that are solved by having an embedded scripting language. First and foremost I direct your attention to the SQLite team. They implemented their testing framework on tcl. Historically a new phone came along that did not support tcl and they had to implement a variation of tcl call th1. This was a fine choice because tcl and th1 have a very small codebase and they are easily ported to new targets. It's that ability to port the tests that allowed the team to leverage their nearly 1M lines of test code. If they had to rewrite the test cases then any number of other issues could have presented.

Where to go for embedded scripting languages? One team that popped is the awesome-go. This is a variation on a project that a group of rubyists developed. The idea was to develop a curated list of projects. I'm not sure how well curated the project is but they cover a large set of projects. In this instance I'm looking for embedded scripting languages(link).

I followed this project page for a very long time. It was the first one and dates way back. project awesome came much later. Buyer beware!

My interest is in 100% go so that projects can be statically linked and not have to worry about more nested dependencies. For example there are multiple lua interpreters. Some are fullblown go and others are API gateways. I have had tremendous success with:

  • otto - javascript
  • golua - lua
  • gotcl - tcl
I elected not to try lisp. I'm not a fan. I also decided not to use a new language (this inspiration for this post is zygomys). I'll never use a customer DSL that someone else designed regardless of correctness or my wrongness as it will be impossible to be in a leadership position. For example the gotcl project is incomplete but it's also a few thousand lines. The basic functionality is there. I also supports channels. If done right you can get a lot of work done right.

Popular posts from this blog

Prometheus vs Bosun

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


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…