Skip to main content

reflection on golang reflection

I'm building a transaction gateway that requires the transcoding message from one schema to another. The messages will originate from the client as a JSON string which is easily parsed by the stdlib and then transcoded to a bytestream based on some schema. The server will process the transaction and return another byte stream which must be parsed according to some schema and then transcoded back to a JSON string and returned to the client.

My challenge, as I review the encoding packages, is how or where do I store the DDL (data definition language) for the byte streams? One easy representation is in the golang struct with the schema contained somewhere in the field types and the tags.

The question, however, is it better to use reflection at runtime or precompute some DDL from the struct or just manually construct the DDL?

Some weeks ago I reviewed some code for an ISO8583 encoder. It did a good job of parsing messages into it's perspective fields, however, in their implementation the user had to provide the schema with every transaction and the first thing the parser did was compute a DDL which it discarded after the parsing was complete. While correctness and clarity are job #1; this explains their decision.

Looking at the stdlib version of the JSON Unmarshal() code I see that they rely on reflection. Quickly reviewing the ffjson package for unmarshal'ing I have no idea what they have done. I do see that they implemented a generator of sorts, however, the public API layer is so obtuse that it feels like this might have been implemented in another language and ported to go. (not a bad thing) but there is a lot more code than the stdlib so it's a matter of complexity over getting the work done.

For now the answer is "working". Fast is a nice problem to have... just not now.


Popular posts from this blog

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.

UPDATE 2017-10-30: With gratitude the CoreOS team has provided updated information on their pricing, however, I stand by my conclusion that the effective cost is lower when you deploy monster machines. The cost per node of my 1 CPU Intel NUC is the same as a 96 CPU server when you get beyond 10 nodes. I'll also reiterate that while my pricing notes are not currently…

eGalax touch on default Ubuntu 14.04.2 LTS

I have not had success with the touch drivers as yet.  The touch works and evtest also seems to report events, however, I have noticed that the button click is not working and no matter what I do xinput refuses to configure the buttons correctly.  When I downgraded to ubuntu 10.04 LTS everything sort of worked... there must have been something in the kermel as 10.04 was in the 2.6 kernel and 4.04 is in the 3.x branch.

One thing ... all of the documentation pointed to the wrong website or one in Taiwanese. I was finally able to locate the drivers again: (it would have been nice if they provided the install instructions in text rather than PDF)
Please open the document "EETI_eGTouch_Programming_Guide" under the Guide directory, and follow the Guidline to install driver.
download the appropriate versionunzip the fileread the programming manual And from that I'm distilling to the following: execute the answer all of the questio…

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…