SQLite3: No Room for Drama

I love SQLite, but some arguments in the article seems contradicting each other.

1. Massive Max DB size vs It can't handle the traffic: If it can't handle the high throughput it doesn't matter how big it can get, because you never get there, you can't do 1 insert/sec and leverage 281 TB storage capability

2. It's just for small projects vs It can't handle the traffic: so it is for small projects, right? I know there are multitude of different types of applications, but when mentioned MySQL/PostgreSQL at the beginning of the article, I thought we would be talking about web/backend related applications.

SQLite has a different mental model, it wants to be simple and close to the code, hence you can't easily setup multi node replication

On the other hand, other databases want to manage your data in isolation, hence they're deployed on a separate machine and have out of box data replication/sharding mechanisms

I know we’re not supposed to whine about the medium but focus on the content. However, on Medium, the medium becomes the content because I can’t even read the damn thing without being accosted by some CTA popover. This is my quiet crusade against authoring on that platform.

I feel a bit bad if it's a human, but I can't even tell if this sort of vapid, uninteresting article was written by an LLM or just someone who is not good at writing and doesn't know much about the topic.

either way though, obviously humans should do whatever writing they but aggregators like HN should reject ones like this.

What the article forgot to mention is that is not suitable for scale out workloads. No concurrent network access.

feels like clickbait

is sqlite used for server side nowadays ? I've always thought this was highly not recommended.