The document discusses N-tier architecture, which divides applications into multiple tiers or layers. A 1-tier architecture has all components on one machine. A 2-tier architecture separates the user interface from data storage. A 3-tier architecture separates the presentation, application/business logic, and data tiers. N-tier architecture provides finer granularity by separating an application into smaller specialized modules or functions across multiple tiers. This improves flexibility, scalability, and the ability to update or replace components independently. A common example is a shopping cart application, which separates components like the user interface, business logic for processing orders, and data storage across tiers.
The Schmooze is a web-based application system that allows the user to define and maintain specific relationships with existing contacts and manage social and business interactions hierarchy with each of those contacts. Schmooze is a web based contact management application system. It will also allow the user to leverage some of the popular social networking tools of the internet such as Orkut, MySpace, Flickr etc and leverage the existing contacts in his/her local e-mail client as well as internet based contact managers like Gmail. Schmooze allows you to store your personal contacts in a centralized secure online database. This centralized contact storage allows you to communicate efficiently with your contacts to share interactions by publishing it as a blog, create an e-commerce transaction, send bulk SMS and e-mail messages etc.
The Schmooze is a web-based application system that allows the user to define and maintain specific relationships with existing contacts and manage social and business interactions hierarchy with each of those contacts. Schmooze is a web based contact management application system. It will also allow the user to leverage some of the popular social networking tools of the internet such as Orkut, MySpace, Flickr etc and leverage the existing contacts in his/her local e-mail client as well as internet based contact managers like Gmail. Schmooze allows you to store your personal contacts in a centralized secure online database. This centralized contact storage allows you to communicate efficiently with your contacts to share interactions by publishing it as a blog, create an e-commerce transaction, send bulk SMS and e-mail messages etc.
Single-SingOn Intranet Portal on DotNEtNuke Corporate intranets for clients to enhance employee productivity and collaboration with features for Forums, Chat, Leave Status, Groups, Knowledge Base, Document Management etc..
Web–based crm application with interactive graphsMike Taylor
Web–Based CRM Application with Interactive Graphs a web based CRM application for its entire sales department to track and record all the activities moving around sales
Case Study for CRM Application For Sales DeaprtmentMike Taylor
CRM Application For Sales Deaprtment with Interactive Graphs a web-based CRM application for its entire sales department to track and record all the activities moving around sales.
discussions about different types of architectures used in web applications, pros and cons of each architecture. MVC design patters and comparison with 3-tier.
A two-tier architecture is an application package architecture in which a presentation layer or interface operates on a customer, and a data layer or data structure gets saved on a server.
Field service application (FSA) refers to a cloud-based system that combines the robust web application and
dynamic mobile application to support field engineers. FSA most commonly caters to the customer who needs
service or repairs of equipment. This application is targeted at the Service industry, intended for the field
engineers. The various service industries register with this for cloud computing services for effective management
of services such as painting, plumbing, Electrician, carpenter etc. This system compliments the software services,
provided by the cloud, with a mobile-based client application, specially designing for the field engineers. This
solution shares a single workflow among the registered tenants thereby ensuring efficient sharing of infrastructure
and also ensuring the security and integrity tenant data.A Multi-tenant Application is an approach to share an
application instance among different customers to reduce overhead the most.
Single-SingOn Intranet Portal on DotNEtNuke Corporate intranets for clients to enhance employee productivity and collaboration with features for Forums, Chat, Leave Status, Groups, Knowledge Base, Document Management etc..
Web–based crm application with interactive graphsMike Taylor
Web–Based CRM Application with Interactive Graphs a web based CRM application for its entire sales department to track and record all the activities moving around sales
Case Study for CRM Application For Sales DeaprtmentMike Taylor
CRM Application For Sales Deaprtment with Interactive Graphs a web-based CRM application for its entire sales department to track and record all the activities moving around sales.
discussions about different types of architectures used in web applications, pros and cons of each architecture. MVC design patters and comparison with 3-tier.
A two-tier architecture is an application package architecture in which a presentation layer or interface operates on a customer, and a data layer or data structure gets saved on a server.
Field service application (FSA) refers to a cloud-based system that combines the robust web application and
dynamic mobile application to support field engineers. FSA most commonly caters to the customer who needs
service or repairs of equipment. This application is targeted at the Service industry, intended for the field
engineers. The various service industries register with this for cloud computing services for effective management
of services such as painting, plumbing, Electrician, carpenter etc. This system compliments the software services,
provided by the cloud, with a mobile-based client application, specially designing for the field engineers. This
solution shares a single workflow among the registered tenants thereby ensuring efficient sharing of infrastructure
and also ensuring the security and integrity tenant data.A Multi-tenant Application is an approach to share an
application instance among different customers to reduce overhead the most.
Software Architecture - Architecture Styles and Patterns-1.pdfjordantsagmo
présente les styles architecturaux et les patterns architecturaux dans de façon claire et concis.vous y trouverez la différence explicitement présenté entre style et pattern architectural
1. N-TIER ARCHITECTURE
The simplest examples of tier architecture are enumerated as 1-Tier, 2-Tier, and 3-Tier. 1-Tier Architecture is the simplest, single tier on
single user, and is the equivalent of running an application on a personal computer. All the required component to run the application are
located within it. User interface, business logic, and data storage are all located on the same machine. They are the easiest to design, but the
least scalable. Because they are not part of a network, they are useless for designing web applications. 2-Tier Architectures supply a basic
network between a client and a server. For example, the basic web model is a 2-Tier Architecture. A web browser makes a request from a
web server, which then processes the request and returns the desired response, in this case, web pages. This approach improves scalability
and divides the user interface from the data layers. However, it does not divide application layers so they can be utilized separately. This
makes them difficult to update and not specialized. The entire application must be updated because layers aren’t separated.
3-Tier Architecture is most commonly used to build web applications. In this model, the browser acts like a client, middleware or
an application server contains the business logic, and database servers handle data functions. This approach separates business logic from
display and data. But, it does not specialize functional layers. Its fine for prototypical or very simple web applications, but it doesn’t measure
up to the complexity demanded ofweb applications. The application server is still too broad, with too many functions grouped together. This
reduces flexibility and scalability. N-Tier Architectures provide finer granularity, which provides more modules to choose from as the
application is separated into smaller functions.
N-Tier and Example
Usually N-Tier Architecture begins as a 3-Tier model and is expanded. It provides finer granularity. Granularity is the ability of a system, in
this case, an application, to be broken down into smaller components or granules. The finer the granularity, the greater the flexibility of a
system. It can also be referred to as a system’s modularity. Therefore, it refers to the pulling apart of an application into separate layers or
finer grains.
One of the best examples of N-Tier Architecture in web applications is the popular shopping-cart web application. The client tier interacts with
the user through GUIs (Graphic User Interfaces) and with the application and the application server. In web applications, this client tier is a
web browser. In addition to initiating the request, the web browser also receives and displays code in dynamic HTML (Hypertext Markup
Language), the primary language of the World Wide Web. In a shopping cart web application, the presentation tier displays information
related to such services as browsing merchandise, purchasing, and shopping cart contents. It communicates with other tiers by outputting
results to the browser/client tier and all other tiers in the network. This layer calls custom tags throughout the network and to other networks.
It also calls database stored procedures and web services, all in the goal of providing a more sophisticated response. This layer glues the
whole application together and allows different nodes to communicate with each other and be displayed to the user through the browser. It is
located in the application server.
In N-Tier Architecture, the business logic tier is pulled out from the presentation tier and, as its own layer, it controls an application’s
functionality by performing detailed processing. For example, in our shopping cart example, this tier completes credit card authorization and
calculates things like shipping costs and sales tax. The tools used to encapsulate an application’s business logic into its own layer include web
services, custom tags, and stored procedures.
The business tier can also be considered the integration layer. Encapsulation allows the application to communicate with the data tier or the
business logic tier in a way that is intelligible to all nodes. Encapsulation is one of the principles of object-oriented programming (OOP) and
refers to an object’s ability to conceal its data and methods. Encapsulated objects only publish the external interface so any user interacting
with them only needs to understand the interface and can remain ignorant as to the internal specifications. This way a user can call all sorts
of services into action by calling the custom tag without having to know the code details of what made communication or implementation
possible. The services just have to be accessible in the custom tag library. Encapsulation in the integration tier also liberates the network from
just one vendor. The integration tier allows N-Tier Architecture to be vendor independent. In the shopping cart example, the application may
have a simple custom tag for searching inventory and providing the most up-to-date, detailed information.