Overview

Best practice network design for a highly scalable, distributed web system has:-

• • No single point of failure. 
  • Fault tolerant
  • Servers are locked down 
  • Defence in depth
  • Load balancing
  • Lowest possible permissions/access for each component
  • Health monitoring for each component

Development Environment

We normally use our own in-house development servers, as they are already setup and configured to our solution server requirements it is cost effective and efficient.

We have automated heart beat monitors which checks the health of the servers and a number of background tasks. In addition to checking the list of known tasks database read & write actions are performed and the available disk space is checked. If the heart beat monitor itself takes more than 5 minutes to run an alert is sent. The heart beat monitor runs every 15 minutes.

The list of tasks that the system will monitor are defined in the class DBTask.

A task is defined by:-

• code which uniquely identifies this task

Server Cluster

A cluster of servers (two or more ) can be setup and the DNS entry for your site can be defined with the IP addresses for each of the servers, this is known as Round-robin DNS

We use Australian web Hosting with 99.99% up time guarantee for non scheduled downtimes

The standard hosting package comes with a 2 hour hardware replacement.

http://www.digitalpacific.com.au/hosting/dedicated-hosting/dedicated-servers/