For web applications, having a separate daemon for sqlite is best practice anyway. SQLite doesn't play nice with multiple concurrent connections (costly locking, the possibility of data corruption). You typically need to offload transactions to a queue in a daemon thread.
It absolutely has good use cases, but those are rather niche. You'll mostly be better off with the traditional postgres etc.