Yeah, and in general the advice is to not do that. However I had more of a slightly diff idea. More like instead of having aweb server + orm. You just write

Yeah, and in general the advice is to not do that. However I had more of a slightly diff idea. More like instead of having aweb server + orm. You just write SQL for an endpoint which maps the storage data to public response. Essentially what the ORM was doing. And if the server is just managing connection and calling then endpoint query. Then packing the data to JSON response. It can just be shared/generic.