Phinza has been built from the ground up to be completely scalable from the small scale deployment of tens to hundreds of users to thousands of users. The architecture supports extremely fast performance while utilizing minimal network and data centre resources. Unlike legacy IT management applications, Phinza is a 100% web based application (not just "Web-enabled"). Configurable compression of data between the server and the browser allows optimal usage of your network, and fast response times. When large scale deployments are needed, clusters of Phinza servers can be deployed to provide 24x7x365 uptimes. To protect against disasters, Phinza servers can also be geographically separated to provide a global highly available cluster.


Small Enterprise Deployment with Disaster Recovery

This deployment caters for the small enterprise to host tens to hundreds of users that also require the capability of high availability without the cost of a Highly Available Cluster. The Phinza standby box is installed at the DR site and a master to slave replication treaty is setup with both the databases. In the event of a disaster at the main site, the standby box is activated and the slave database is promoted to be the master. The users are switched over to the Disaster recovery site and the server. After the main site is recovered, the slave database is re-synced with the master and the master server and the master database and made operational.


Small Enterprise Deployment

This is a typical Phinza deployment to the small enterprise that can scale from tens of users to hundreds of users. The Phinza box is shipped to the customer as a rack appliance that fits any standard data centre rack. The Phinza box is pre-configured with the Phinza web application server and database server modules with all the settings configured for the end user to be up and running in the least possible time. The box itself is highly reliable with top shelf redundant components and the database sitting on a RAID array. Whilst this would give upwards of two nines (99%) reliability, it does not protect the enterprise against complete disaster.


Small Enterprise Deployment with Disaster Recovery

This deployment scenario sees Phinza deployed into a large enterprise's data centre as a High Available (HA) cluster. This data centre is assumed to have the equipment and personnel to host a large scale web infrastructure. The Phinza web application server tier consists of 2 or more servers in a loose load balanced cluster. This cluster is fronted by a load balancer. The load balancer directs the user to the available server in the pool. The Phinza database tier will consists of 2 or more servers in a close knit cluster configuration. The servers will host HBA's (Host Bus Adapters) that connect to a Storage Area Network (SAN) to hold the shared file system that hosts the database. This deployment protects the environment against component and server hardware failures at each tier. This provides upwards of three to four nines (99.9% to 99.99%) availability, but does not protect against wholesale site disaster.


Large Enterprise Data Center based Deployment with Disaster Recovery

This deployment scenario is similar to the data centre based clustered environment, but adds the option of a standby server and database at the disaster recovery site. A master to slave replication treaty is setup between the two databases and the failover and recovery scenarios are very similar as described previously. In the event of a disaster at the main site, the standby box is activated and the slave database is promoted to be the master. The users are switched over to the Disaster recovery site and the server.