Enterprise Application Architecture mode N-tier multi-tier architecture

Let's look at the classic 3-tier architecture and see:

The platforms involved can be:

Ruby on Rails, Java EE, ASP, PHP, ColdFusion, Perl, Python

The data transfer using protocol between tiers can be:

SNMP, CORBA, Java RMI,. NET Remoting, Windows communication Foundation, sockets, UDP, Web services, etc.

The 3-tier architecture we often talk about is the N-tier architecture, and the usual n-tier is this:

This is only a logical diagram, the real environment implementation is some layers on the same server, some layers are split on different physical servers. This depends on how the system is used and is limited by the rules environment policy.
Take a look at the architecture diagram for the DDD-based. NET Platform:

Look at the following slightly more complex architecture:

Example diagrams for complex applications and logic layers:

The above diagram mentions load balancing, application servers, Web servers, file servers, workflow services, mail servers. People who have a bit of work experience can't understand.
Not in detail here.

Other tips:

The architecture is designed to achieve the following objectives:

• Reliability (Reliable). Software systems are extremely important for the business and management of the user, so the software system must be very reliable.
• Security (secure). The commercial value of the transaction undertaken by the software system is very high, and the security of the system is very important.
• Scalability (scalable). The software must be able to maintain reasonable performance when the user's usage rate and the number of users increase rapidly. Only in this way can we adapt to the market expansion possibilities of the users.
• Customizable (customizable). The same set of software can be adjusted according to the different customer base and the change of market demand.
• Scalability (extensible). In the advent of new technologies, a software system should allow the introduction of new technologies to extend the functionality and performance of existing systems.
• serviceability (maintainable). The maintenance of software system includes two aspects, one is to eliminate the existing errors, and the other is to reflect the new software requirements to the existing system. An easy-to-maintain system can effectively reduce the cost of technical support.
• Customer Experience (Experience). Software systems must be easy to use.
• Market timing (time to markets). Software users face competition from peers, and software providers also face competition from peers. It is very important to compete for the market opportunity with the fastest speed.

Software architecture is an abstraction of the runtime elements of a software system, a software system may have many layers of abstraction, or it consists of multiple business processes, each abstraction or each business process has its own software architecture.
Software architecture is the art of balance.

I hope it will be helpful for you to come here today.

Data collection and integration, hope that your software development and enterprise information can help. Other articles you might be interested in:
N-tier Entity Framework Open Source Project Introduction
IT Infrastructure planning scenario one (network system planning)
IT Infrastructure Planning Program II (computer system and computer room planning and planning)
IT Infrastructure Planning Scenario III (IT Infrastructure software and system planning)
Evolution of real-time measurement system of enterprise application performance
A few examples of cloud computing reference architectures
Smart Mobile Guide Solution Brief
Evolution of human resource management system

If you want to know more software development, system it integration, enterprise information and other information, please follow my subscription number:

Petter Liu
Source: http://www.cnblogs.com/wintersun/
This article is copyright to the author and the blog Park, Welcome to reprint, but without the consent of the author must retain this paragraph, and in the article page obvious location to the original link, otherwise reserves the right to pursue legal responsibility.
The article was also published in my Independent blog-petter Liu blog.

Enterprise Application Architecture mode N-tier multi-tier architecture