But while you need to do everything with a JSON1 extension for managing the json ( https://www.sqlite.org/json1.html ).
Postgress has build-in v8 javascript functions to manage this ( as stated before). Which makes it much more useable.
There's a good library for .net that handles postgress documents, which has an insane amount of usefull functions ( https://martendb.io/documentation/documents/ ). I think halve of those wouldn't be possible on another database.
Also see "Many Small Queries Are Efficient In SQLite": https://sqlite.org/np1queryprob.html
Round-trips and small queries don't have anything related to my comment?
The main reason why main client-server databases have so many built-in functions is because of the round-trips. Let's say you want to filter rows based on the result of some function, if your function is implemented client-side, then the database would have to send each row to the client.
"Relational database engines act as bandwidth-reducing data filters." (https://www.sqlite.org/whentouse.html)