Resolve Project Server advantages?

I'm trying to understand what the benefits are of running a dedicated instance of Resolve Project Server over running a Resolve PostgreSQL database on a NAS or Linux server?

Is there any additional magic that happens through the Resolve Project Server application that a properly configured and optimized PostgreSQL installation on Linux/NAS isn't able to manage?

I'm speaking particularly in the context of collaborative projects here as I'm not really seeing any outward advantages of going down the Project Server route.

Hope someone can shed some light on this.

I'm also interested in this? Did you find any further info or documentation on it?

Thanks

In terms of performance there doesn't seem to be any optimizations, you still have to do those manually, like configure the amount of RAM it can use. The advantage of the Project Server I would say is the ability to export a database access key which makes it easy to connect even for users that don't have any experience in setting up a PostgreSQL server.

Also, it's a GUI for maintenance commands like createdb, reindexdb and vacuumdb. If you have Project Server installed (and therefore PostgreSQL) you can run those directly from the Project Server app. You can't run them on a Resolve client unless the tools are installed on the client.

There's also the ability to easily set the network interface for the server, if you have more than one.

I find installing a project server in a standalone Mac or Windows is easier than trying to configure a QNAP NAS. We run a separate PostgresSQL backup.

I went down the PostgreSQL Docker Container (on a QNAP NAS) route - far more efficient.

Project Server is a waste of compute resources from my perspective. There's no Linux instance for headless installs and I didn't want to waste precious RAM overhead and CPU cycles on a pointless MacOS or Windows VM just for a PostgreSQL server with a pretty front-end GUI.

For the average end-user it may do the job though.

The Database Access Key is simply an XML file which anyone can also manually create... and the database passwords are also in cleartext - hardly secure.

Code: Select all

<?xml version="1.0" encoding="UTF-8"?>
<DBAccessKey>
  <hostIPAddress>*** IP ADDRESS or FQDN ***</hostIPAddress>
  <dbName>*** DATABASE NAME ***</dbName>
  <dbUsername>*** DATABASE USER ***</dbUsername>
  <dbPassword>*** DATABASE USER PASSWORD ***</dbPassword>
</DBAccessKey>