I recently encountered an interview problem that involved answering various analytical questions over some number of delimited data files. It mentioned running on a laptop, and asked the interviewee to consider scalability in terms of data volume and extensibility in terms of answering new questions. Like many interview problems, the …
I'm migrating my blogs on various sites (primarily blogspot) to github pages. I like specifying the content in markdown and having revision control.
The default static site generator on github pages is Jekyll, which is written in Ruby. I tried it out briefly, but decided to go for a generator …
Modern Python tooling for managing dependencies, testing, and linting
I've been really fortunate through the years to be surrounded by people who are dedicated to continuous learning and improvement. A few years ago, I put together a reading list as part of an engineering department reboot. I updated it late last year. I have rough reading/discussion times for some of it.
Read on →
Now that I've got my project getting packaged up in a docker image, the next step in this POC is to look at platforms for running docker. The only PaaS that I am familiar with now is Pivotal Cloud Foundry, which we used at my last job to deploy Spring Boot executable jars. PCF was working on a docker story, not sure how far that got. It looks like they are pretty bought into Kubernetes these days.
Converting from the transmode gradle plugin to the bmuschko remote api gradle plugin was pretty straightforward. Other than importing and applying the plugin, the code to get local docker image creation working is as follows
At last we get to some Docker in this Docker example.
The next step was to add some tests. The tests that came with the demo controller used a Spring feature I was not familiar with, MockMvc. The Spring Guide "Testing the Web Layer" provides a good discussion of various levels of testing, focusing on how much of the Spring context to load.