Does setting `SERVE_APP=false` on an API-only instance:
1. Directly mitigate database connection pool exhaustion?
2. Significantly reduce RAM/CPU usage by eliminating the Admin App overhead?
Confirming the best practice for production scaling. Thank you.
Are you seeing errors around connection pool exhaustion?
The Admin panel is a single page application that makes API requests into the DIrectus API. It’s just serving up static javascript files, so on it’s own won’t make a difference to resource consumption.
For production scaling, you could look at using our Direcuts Cloud, alternatively you can look at the community helm chart over here.
It doesn’t directly affect the database connection pool or even ram/cpu as the app is just a static html+css+js bundle, and not a running piece of backend itself. That being said, having users actively using the studio will of course use resources as they’re making API calls to power that studio. There’s no difference between having the studio enabled and not using it and having it disabled.