The Tony’s Chips web site is to be moved from and external hosting solution to an internal solution. In addition, the site will be redesigned to enable customers to place orders. These are two separate work tasks that should be treated separately and performed by different team members. There are many options for hosting the web site internally, including software choices to hardware architecture. This document will review the tasks that need to be performed, document the process of performing those tasks, and justify the software and hardware choices.
There are a couple different alternative to how this web site is hosted. The company could host the ...view middle of the document...
Even in the case of large database-driven web applications, companies tend to move to an internally-hosted paradigm once they have the resources necessary to actualize this desire. It is important that this be well thought out and planned for. It is not an inexpensive task.
Migrating the System
The first step in migrating the web site from an externally hosted service to an internal system is to get the infrastructure in place. This includes the physical computers that will be used, the software servers that will be installed on these computers, the network configuration, the wide area network connectivity, and the necessary firewall. Once all of this is in place, the content of the external web site should be replicated to the internal system, as it currently is. Then, after testing the internal web site via the IP address that points to the internally-hosted version, the systems administrators can update the DNS record for the web-site’s domain name to point to the internally hosted version. This can take a couple days to fully propagate across the major DNS backbone on the internet. During that time, some traffic will go to the internal site and some will go to the external site.
There will be no down-time as far as the users of the site are considered. However, some data that is stored as a result of user-interaction may not be record at the new site. This will require that the old site be left running for a business week. After every day, the old site should be checked for any new data transactions. Any found should be migrated the new site. While this method place more work on the staff of the company, it results in zero downtime for users of the site. The work to be performed in this part of the project can be broken down into: Planning and Analysis, Physical Setup, Software Installation, Code Replication, Data Migration.
As can be seen in the above Gantt Chart, a lot of the tasks that are taken during the process of migrating the existing site from an externally hosted service to an internally hosted system can occur concurrently. For instance, installation of the web server and the database server can occur at the same time. This is assuming that the web server and the database server are on two different machines.
The system software that will be used is rather standard for a web site. The paradigm hat is chosen revolves around a Linux, Apache, MySQL, PHP (LAMP) model. The security features available within many distributions of Linux are far better than would be available on Windows. In addition, everything in a LAMP model is freely available. An alternative model would use Windows and IIS. However, Windows and IIS are only available commercially. In contrast, Linux and Apache are free systems that are widely supported and are, by far, the most widely-used platform for hosting web sites. In addition, the use of PHP and MySQL is also free. The web site could also be set up with something like Adobe...