1 vote
As the title suggests, it would be really good to see Devolutions introduce the ability to have the back-end database for a DVLS deployment be PostgreSQL instead of depending on Microsoft SQL Server.
You've already made some headway by providing a method for DVLS itself to be installed on Linux as per Install Devolutions Server for Linux | Devolutions Server | Devolutions Documentation and ScriptLibrary/DVLSForLinux at main · Devolutions/ScriptLibrary -- but it would be fantastic to see it taken a step further. For self-hosted infrastructure that is air gapped and does not have direct internet access (i.e., has no potential to leverage Devolutions Workspace/Hub, or other SaaS components which require internet access, etc), this would drastically reduce the compute requirements for running a highly available and fault tolerant DVLS deployment in such an environment without cumbersome MSSQL servers with costly licensing requirements.
Companies such as Veeam realized this a few years ago and have since transitioned to PostgreSQL being the preferred database type on greenfield deployments after more than two decades of Microsoft SQL Server Express (or Standard/Enterprise)~ being the defacto (and only) choice.
While I don't necessarily expect that Devolutions would go down the same path as Veeam and deliver an entire pre-hardened, vendor-managed (STIG compliance), secure-by-design appliance such as with the newer Veeam Software Appliance (Veeam Software Appliance: Fast, Secure, and Simplified) (though, I would love it if Devolutions were considering or working on something like this), simply adding PostgreSQL as a supported database type for hosting the Devolutions Server (DVLS) database would be a really big improvement that we would be excited to see.