How about the ASP.NET MVC (Model View Controller) framework?
http://weblogs.asp.net/sco
Main Topics
Browse All TopicsHi experts,
I would like to know the best design pattern for pure database driven asp.net web application for your experiences, please give me the pattern name and why it is so best...
My application have high database usage....please suggest me.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
How about the ASP.NET MVC (Model View Controller) framework?
http://weblogs.asp.net/sco
I recommend using CSLA framwork, http://www.lhotka.net/csla
We have asp .net that is used by about 20,000 users and CSLA's features like caching of objects, etc greatly reduce the database roundtrips. Although the latest version of the framework looks like its geared towards silverlight, we use it with regular asp.net pages.
i believe you are a bit confused.
MVP/MVC are presentation patterns.
Before anyone can really site other architectural patterns we would need to know more about the non-functional requirements that you are seeking to reach. As an example, putting in an application server can offer great benefits in terms of reusability, scalability, and availability but can hurt you in terms of cost. All of these types of decisions are generally trade offs so we really need to know what is important to you.
Cheers,
Greg
The kind of project i'm doing is purely a web analytics system, where in i'm using log parser to updated the database using incremental parsing, so i will be left with 1000's of records in DB, now from UI i write various queries to get statistics,,,,my main point of interest is re-usuability and easy to add new funtionalities...so what pattern do you suggest for this application if you are a developer.
As i'm at junior level,i couldn;t easily get from my experience, i can start with MVC/MVP but really i'm not sure whether i'm doing right or not..
i think you are right i'm bit confused with patterns...
Business Accounts
Answer for Membership
by: fanopoePosted on 2009-08-18 at 07:18:54ID: 25123483
not sure what you mean by pattern name, but N-Tier is often used in high database usage systems. I don't know what database back end you have, but since it is high usage, I would hope you are using a major player (Oracle, SQL Server, MySQL, etc....) - at least one that supports compiled procedures.
I use pre-compiled procedures on the database, because nothing is better at acting on data than the database itself. I access this with a Data Layer that simply receives input variables, makes a database call with them, and returns a value or an error. I access the data layer via a business layer that makes decisions that are unique to the business environment. That is accessed via the presentation layer (web pages) that accepts input from and gives feedback to the users.
The reason it is so good is that, if your company decides to switch from say oracle to mysql to save licensing costs, all you have to do is set up the database with the same procedure names and adjust your datalayer to use mysql instead of oracle. Additionally, if another branch of your company wants to use your application but they operate differently, perhaps because of geography, you can deploy the application as is and only need to update the business layer to represent their rules.
By compartmentalizing these components, you make big changes much easier to accomplish.
I hope that helps