Website system architecture:

[pic]

Description:

The new proposed architecture that can be used to deploy the company’s website has been shown above. According to the figure it can be seen that the web-server has been hosted internally behind the company firewalls. Similarly, database servers will also be hosted internally. Though, a backup of the database server will be stored on a third party data center. The line in a dotted form shows that the data base server will be connected to database objects only at the time of disaster or at times when back-up is required. So, this kind of setup is a hybrid kind of architecture, where in both external (third party) servers are used and internal servers are used (one for mainstream usage and other for emergencies and disasters).

Also, the web server that will be used will be IIS (Windows), Operating system – Windows, Database- MySQL.

The reason for choosing this combination of operating system, webserver and database is that Windows based technologies have a good support system and a better customer service than other open source alternates.

Justification of the proposed system architecture:

The system architecture makes the best of both the worlds. It provides the system robustness with third party backups. These backups can be put to use when internal hosting collapses due to some or the other reason. Also, customized firewalls and server ownership can be enjoyed by the company because of internal hosting of webserver and database servers.

Discussion of alternatives:

For implementing the concerned website project, following alternatives could hav...

1 2 3 4 5 access accord addit ahead along alreadi also altern analysi applic architectur aspect attach back back-up backup bad base batch behind best better brief broken capabl care case categori caus center chang chart check choos chunk click code collaps combin compani compat comput concern configur confirm connect consid contain content control copi could creat creation criteria current custom data data-cent databas dataserv decid defin deploy descript design detail develop diagram disast discuss doesn done dot downtim due dump ecommerc either emerg enabl enjoy ensur enter environ establish etc evalu exist experi expos extern fact featur feedback figur firewal first follow form four full gain gantt gateway generat get give go good greater guarante handl harden help higher host hybrid ii iis/operating implement includ info inform infrastructur instant integr intern issu justif keep keyword kind latenc later less like limit line list live mainstream maintain mainten major make measur mention microsoft minim minimum model modul multipl mysql need new note number object one onlin open oper order organ overhead ownership packag page parti path payment per perform phase pic prepar present process produc product program project propos provid purchas put rang readi reason recoveri reduc relat request requir respect respons result resum robust routin say scalabl schema screen script sdlc search secur see seen segment select sens sent server servic setup show shown similar singl site sitemap softwar sourc step store stress string submit success support system take taken task team technolog tell test therefor thing third though threshold thus tight time total traffic transit trivial troubleshoot trust usabl usag use user view wait web web-serv web-sit webserv websit wherein whether whole window wirefram won world would