216 karma · joined August 10, 2013
Working for this company taught me stuff I really didn't want to know about...
The history of this system is pretty organic, lots of experimentation. Started with Postgres, but that was too slow if a select statement returns tens of thousands of rows. MariaDB was way faster but became erratic once we passed about 2 billions of records. Now with SQLite we are at about 180 GB, about three years of data so far, so not really "big data" territory yet.
Constantly looking for better alternatives. InfluxDB looks promising, but maybe we'll switch to a "hot/cold" approach instead, keeping whole "cold" days as JSON objects in JSONB fields in Postgres again while storing "hot" data in SQLite. We'll see...
So far the system has been rock solid. In the last few weeks we went live for real, now storing about 2k records a second. Not a problem so far.
But try telling people you're using SQLite to store critical data...
I love how simple the language is. Quick and easy to learn, small footprint, embeddable. For quite a while I used to prototype simple web services in Tcl, then convert to C for speed. The Tcl versions were so much easier to write, adapt, and debug, and had more features, because in C at some point I thought, meh, don't really need this...
let A0 = 123
let A1 = 234
let A2 = 345
rightstring B3 = "asd"
leftstring B5 = "foo"
label B11 = "bar"
goto B11 A0
Just a textual description of what your spreadsheet should look like. Gosling had it right back in the 80s ;)Bad sign.