Project Development

Hi,

We design website architecture to allow long term development flexibility and scalability.Planning the website , or any other software, in phases will help your clients feel comfortable doing business with you.

When building the web site, implementing a flexible architecture composed of pluggable
components allows you to add new features—such as the shopping cart, the departments list, or the product search feature—by coding them as separate components and plugging them into the existing application.Generally, the architecture refers to splitting each piece of the application's functionality into separate components based on what they do and grouping each kind of component into a single logical tier.
The three-tier architecture has become very popular because it answers many of the problems
discussed so far by splitting an application's functionality unit into three logical tiers:
• The presentation tier
• The business tier
• The data tier
The presentation tier contains the UI elements of the site, and includes all the logic that
manages the interaction between the visitor and the client's business. This tier makes the whole site feel alive, and the way you design it is crucially important to the site's success. Because your application is a web site, its presentation tier is composed of dynamic web pages.
The business tier (also called the middle tier) receives requests from the presentation tier
and returns a result to the presentation tier depending on the business logic it contains. Almost any event that happens in the presentation tier results in the business tier being called (except events that can be handled locally by the presentation tier, such as simple input data validation). For example, if the visitor is doing a product search, the presentation tier calls the business tier and says, "Please send me back the products that match this search criterion." Almost always, the business tier needs to call the data tier for information to respond to the presentation
tier's request.
The data tier (sometimes referred to as the database tier) is responsible for storing the
application's data and sending it to the business tier when requested. Almost every client request finally results in the data tier being interrogated for information (except when previously retrieved data has been cached at the business tier or presentation tier levels), so it's important to have a fast database system.

For ORM and MVC please refer the link below, this might help you out.

http://stackoverflow.com/questions/1004295/asp-net-mvc-and-orm-selection
If my answer helps you out please select it accepted

cheers,
Thanks

1 Reply

Know the answer? Post it — somebody with the same question will find it here.

Shakuntala Gaur14y ago
Hi,

We design website architecture to allow long term development flexibility and scalability.Planning the website , or any other software, in phases will help your clients feel comfortable doing business with you.

When building the web site, implementing a flexible architecture composed of pluggable
components allows you to add new features—such as the shopping cart, the departments list, or the product search feature—by coding them as separate components and plugging them into the existing application.Generally, the architecture refers to splitting each piece of the application's functionality into separate components based on what they do and grouping each kind of component into a single logical tier.
The three-tier architecture has become very popular because it answers many of the problems
discussed so far by splitting an application's functionality unit into three logical tiers:
• The presentation tier
• The business tier
• The data tier
The presentation tier contains the UI elements of the site, and includes all the logic that
manages the interaction between the visitor and the client's business. This tier makes the whole site feel alive, and the way you design it is crucially important to the site's success. Because your application is a web site, its presentation tier is composed of dynamic web pages.
The business tier (also called the middle tier) receives requests from the presentation tier
and returns a result to the presentation tier depending on the business logic it contains. Almost any event that happens in the presentation tier results in the business tier being called (except events that can be handled locally by the presentation tier, such as simple input data validation). For example, if the visitor is doing a product search, the presentation tier calls the business tier and says, "Please send me back the products that match this search criterion." Almost always, the business tier needs to call the data tier for information to respond to the presentation
tier's request.
The data tier (sometimes referred to as the database tier) is responsible for storing the
application's data and sending it to the business tier when requested. Almost every client request finally results in the data tier being interrogated for information (except when previously retrieved data has been cached at the business tier or presentation tier levels), so it's important to have a fast database system.

For ORM and MVC please refer the link below, this might help you out.

http://stackoverflow.com/questions/1004295/asp-net-mvc-and-orm-selection
If my answer helps you out please select it accepted

cheers,
Thanks