Comment by mst

There are plenty of reasons.

  * Single file to back up
  * Unix fs permissions sufficient for security
  * Simplicity valuable over write concurrency
  * Ability to write functions/aggregates/collations in the language you're embedding sqlite in
  * No need for maintaining and securing a system daemon

This article isn't, at all, about a problem with SQLite. It's about graphite shipping a stupid postgres schema. Had they used text for the column like anybody who knows how to use postgres would recommend, the graph names would've transferred fine.

TL;DR - graphite devs don't understand postgresql, graphite user misdiagnoses the problem and blames sqlite for it.