your database front-end

Server Outage Notice: will be transfering to a new Server on Friday 25th @ 7pm MST

Installation Overview

dbFront can be fully set up in 3 minutes or less but the practical decisions about where and how to set it up mean that it may take longer.  Some of the decisions that need to be made upfront are:

  • deciding if it should be set up in a DMZ (so that external users can access it without compromising security),
  • finding a server or servers to host it,
  • doing the actual setup and testing,
  • giving specific users access.

If you are not sure which network configuration you should use, then please read the Setup Options section below which explains the different setup options.

Setup Steps

The dbFront installer will install both the Web Application and the Service correctly.   If you installed everything on the same server then you can skip to step 3 where you set up the database connections.  If you chose a manual installation, or if your situation is more complex then you can review the settings in steps 1 and 2.

  1. Setup the Webserver with the dbFront UI web application
  2. Setup the Application server with the dbFront Application Service
  3. Update the Application Server to allow database access

Setup Options

There is a wide variety of network setup options available.  The following two sections will compare two of the main options but the installation can usually be tailored to suit your network needs. 

Single Server Setup

dbFront can be run entirely from a single server.  This server could even be the database server.  But just because it can be done does not mean that it should be done.
A single server installation should only be considered in situations where:

  • The server is internal to your network (security is not a serious consideration)
  • No access to the internet is permitted (or only via VPN),
  • The database and the application loads are small.


  • A single server to install, maintain and backup.
  • Potentially fast if the server is not overloaded because the only network traffic is between the server and the client since all other traffic between the database, application server, and web server are internal.


  • Difficult to properly secure.  Should NOT be exposed to the web or only via VPN access.
  • A single and much easier target for an attacker to compromise.
  • The server load will be too high for larger or high load databases.

Distributed Server Setup (including DMZ)

Network Diagram with separate servers

The optimal setup is to spread the Database, Application Server and Web Application over three servers.  The Database and Application Servers should be installed inside your internal network.  The Web Application server should be installed in a DMZ.

A DMZ is a specially protected network zone created for web servers that sits between your internal network which is usually considered the safe zone and the fully exposed internet.  Web servers in the DMZ are partially exposed to the internet so that users on the internet can access them but this access is limited to make it difficult for attackers to abuse these servers.


  • Most robust setup since three servers share the workload.
  • Most secure setup since an attacker would have to compromise multiple servers before they could get into the network.


  • Most complex setup.  Need to configure and manage the interaction between multiple servers and firewalls.
  • Highest potential latency because a full request to the database will involve multiple network hops as the request passes between the various firewalls and servers back to the client browser.

Next Step

Once the layout of the infrastructure has been decided then the next step would be to set up the webserver and install the dbFront UI.

Content you want the user to see goes here.