James Turnbull

Personally like Linux a lot. It is worth it for the first-class docker support. James Turnbull had an article reviewing the XPS 13 last year. It is what I would recommend: https://www.kartar.net/2018/03/dell-xps-13-aka-2018-is-the-year-of-lin…

Here's a dump of blogs I follow that have lots of devops-oriented contents. http://www.kartar.net/ http://www.kitchensoap.com/ http://www.masterzen.fr/ http://blog.nistu.de/ http://www.jedi.be/blog/ http://www.krisbuytaert.be/blog/ http://www.unixdaemon.net/ http://www.rottenbytes.info/ http://blog.lusis.org/ http://bitfieldconsulting.com/ http://agilesysadmin.net/

The raw data in the spreadsheet, which I have continued to update and is now up to 15 databases with 30 characteristics each, is indeed applicable to both people who want to pick up a database and use it in their monitoring stack, or who want to use a time series database for another purpose. Some of the newer additions like Warp10 and Akumuli for example have comments about being great choices for sensor applications and those who need highly performant local time series storage written in C++. That's a good point about the compression. I bundled that all in the row 'bytes per point after compression' which gives the end result for each database but I haven't noted which ones actually compress. However, there is 1 database that uses lossy compression so that is noted. That's all in row 11 currently. Someone else also raised the clustering question and I added a row for 'dynamic cluster management' to address the question of whether you could just horizontally scale by adding a node without bringing the system down. The performance numbers are a big problem regardless of how they are calculated. Firstly, I'd like to address the issue of whether having them or not is important. I believe it's incredibly important to have some kind of idea up front before investing time trying out a database. If we agree that performance numbers are essential, especially considering the database list is up to 15 and growing and we need some kind of method to reduce the number to trial,…

For added perspective here's another recent review of another engineer who made the switch: https://www.kartar.net/2018/03/dell-xps-13-aka-2018-is-the-year-of-lin…

Some useful background info in https://www.kartar.net/2017/10/prometheus/ on why Turnbull wrote the book, despite being one of the maintainers for a competing monitoring tool, Riemann.

After using https://github.com/inconshreveable/log15 for Go, I become sold on structured logging (read more http://gregoryszorc.com/blog/category/logging/ and https://kartar.net/2015/12/structured-logging/). I've decided that Rust must have a strong structured logging solution, and so I present: slog-rs. I believe it reached a level of usability justifying sharing with a wider audience. See slog-rs features: https://github.com/dpc/slog-rs#features Happy logging!

I did exactly that with Puppet as an experiment: http://kartar.net/2013/12/building-puppet-apps-inside-docker/. Works reasonably well. I will say though that the Dockerfile syntax is, IMHO, much easier to use than Puppet/Chef/etc. Disclaimer: I work at Docker and previously worked at Puppet Labs.