Design decisions
-
After a day long meeting trying to come up with a new design for an existing website there were three proposals. Senerio A is the current model, Senerio B and C has been proposed by someone else, and Senerio D is my proposal. This is for a web site that has a potential user base of 11,000+ users who require minimal time (they want instant access) to view the data. Data security is essential and scalability, performance and ease of maintenance are required. I would value opinions as to the pros and cons of these senerios. Senerio A: Data from SQL Server database is loaded into a XML file stored locally by a windows service. Webpages read XML file, create a dataset from it and fill in datagrid, etc. Every 30 minutes XML file is refreshed from database using another windows service. Senerio B: Data from SQL Server database is loaded into a XML file stored locally by a windows service. Webpages read XML file and create DataSet which is cached. Page uses cached DataSet to fill datagrid, etc. Every 30 minutes XML file is refreshed from database. Senerio C: Data from SQL Server database is loaded into a XML file stored locally by a windows service. Webpages read XML file and streams it to client. client filters and displays data using javascript. Every 30 minutes XML file is refreshed from database using another windows service. Senerio D: Webpages access Data Layer object Data Layer object access cache or database and gets DataSet DataSet is cached with expiration policy Webpages use dataset returned from Data Layer to fill datagrid, etc.
-
After a day long meeting trying to come up with a new design for an existing website there were three proposals. Senerio A is the current model, Senerio B and C has been proposed by someone else, and Senerio D is my proposal. This is for a web site that has a potential user base of 11,000+ users who require minimal time (they want instant access) to view the data. Data security is essential and scalability, performance and ease of maintenance are required. I would value opinions as to the pros and cons of these senerios. Senerio A: Data from SQL Server database is loaded into a XML file stored locally by a windows service. Webpages read XML file, create a dataset from it and fill in datagrid, etc. Every 30 minutes XML file is refreshed from database using another windows service. Senerio B: Data from SQL Server database is loaded into a XML file stored locally by a windows service. Webpages read XML file and create DataSet which is cached. Page uses cached DataSet to fill datagrid, etc. Every 30 minutes XML file is refreshed from database. Senerio C: Data from SQL Server database is loaded into a XML file stored locally by a windows service. Webpages read XML file and streams it to client. client filters and displays data using javascript. Every 30 minutes XML file is refreshed from database using another windows service. Senerio D: Webpages access Data Layer object Data Layer object access cache or database and gets DataSet DataSet is cached with expiration policy Webpages use dataset returned from Data Layer to fill datagrid, etc.
Is the SQL server a remote server or local?
-
Is the SQL server a remote server or local?
On a seperate and dedicated machine. The application is also using ASP.NET 2.0
-
After a day long meeting trying to come up with a new design for an existing website there were three proposals. Senerio A is the current model, Senerio B and C has been proposed by someone else, and Senerio D is my proposal. This is for a web site that has a potential user base of 11,000+ users who require minimal time (they want instant access) to view the data. Data security is essential and scalability, performance and ease of maintenance are required. I would value opinions as to the pros and cons of these senerios. Senerio A: Data from SQL Server database is loaded into a XML file stored locally by a windows service. Webpages read XML file, create a dataset from it and fill in datagrid, etc. Every 30 minutes XML file is refreshed from database using another windows service. Senerio B: Data from SQL Server database is loaded into a XML file stored locally by a windows service. Webpages read XML file and create DataSet which is cached. Page uses cached DataSet to fill datagrid, etc. Every 30 minutes XML file is refreshed from database. Senerio C: Data from SQL Server database is loaded into a XML file stored locally by a windows service. Webpages read XML file and streams it to client. client filters and displays data using javascript. Every 30 minutes XML file is refreshed from database using another windows service. Senerio D: Webpages access Data Layer object Data Layer object access cache or database and gets DataSet DataSet is cached with expiration policy Webpages use dataset returned from Data Layer to fill datagrid, etc.
Analyzing a complete XML file and then creating the webpage ? is it just me or :doh:? The DataSet IS xml and it can be kept in memory and you can bind it directly to the grid (or first put in a view). I'd go for D for adaptability (DAL component is always good) or B if it has to have a xml file. (suppose the databaseserver is down you'd still be able to create the webpage according to the xml file.) Good luck. No hurries, no worries.