From your link: Classic Serverless: The database engine runs within the same process, thread, and address space as the application. There is no message passing

From your link: 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. It sounds like this is neo-serverless but serverless nonetheless.