One thing to note: the bottleneck demonstrated here is in write transactions per second, not in GB|rows inserted per second or anything. The vast majority of b

One thing to note: the bottleneck demonstrated here is in write transactions per second, not in GB|rows inserted per second or anything. The vast majority of businesses will never hit 400qps for writes anyway (and many of the ones that would could throw a sharding strategy at the problem), but just having a lot of data being written isn't sufficient to make sqlite an untenable solution; problems only arise when the insertions of that data need to be extremely fine-grained.