"time series databases" entries

Four short links: 19 November 2015

Four short links: 19 November 2015

Javascript Charting, Time-Series Database, Postgresql Clustering, and Organisational Warfare

  1. plotly.js — open source Javascript charting library. See the announcement.
  2. Heroic — Spotify’s time-series database, built on Cassandra and Elasticsearch. See the announcement.
  3. Yoke — high-availability Postgresql cluster with automated cluster recovery and auto-failover.
  4. Ten Graphs on Organisational Warfare — Simon Wardley in a nutshell :-)
Four short links: 1 July 2015

Four short links: 1 July 2015

Recovering from Debacle, Open IRS Data, Time Series Requirements, and Error Messages

  1. Google Dev Apologies After Photos App Tags Black People as Gorillas (Ars Technica) — this is how you recover from a unequivocally horrendous mistake.
  2. IRS Finally Agrees to Release Non-Profit Records (BoingBoing) — Today, the IRS released a statement saying they’re going to do what we’ve been hoping for, saying they are going to release e-file data and this is a “priority for the IRS.” Only took $217,000 in billable lawyer hours (pro bono, thank goodness) to get there.
  3. Time Series Database Requirements — classic paper, laying out why time-series databases are so damn weird. Their access patterns are so unique because of the way data is over-gathered and pushed ASAP to the store. It’s mostly recent, mostly never useful, and mostly needed in order. (via Thoughts on Time-Series Databases)
  4. Compiler Errors for Humans — it’s so important, and generally underbaked in languages. A decade or more ago, I was appalled by Python’s errors after Perl’s very useful messages. Today, appreciating Go’s generally handy errors. How a system handles the operational failures that will inevitably occur is part and parcel of its UX.