I, too, think of "classical serverless" rather than "neo-serverless": https://www.sqlite.org/serverless.html https://www.sqlite.org/serverless.html ------ Rec

I, too, think of "classical serverless" rather than "neo-serverless": https://www.sqlite.org/serverless.html https://www.sqlite.org/serverless.html ------ Recently, folks have begun to use the word "serverless" to mean something subtly different from its intended meaning in this document. Here are two possible definitions of "serverless": Classic Serverless: The database engine runs within the same process, thread, and address space as the application. There is no message passing or network activity. Neo-Serverless: The database engine runs in a separate namespace from the application, probably on a separate machine, but the database is provided as a turn-key service by the hosting provider, requires no management or administration by the application owners, and is so easy to use that the developers can think of the database as being serverless even if it really does use a server under the covers.