Design, deploy, and manage a scalable e-commerce website using Windows DNA (1) -- from M $

Design, deploy, and manage a scalable e-commerce website using Windows DNA
What we want to learn today is the best practice about scalability, availability, and reliability. We will discuss load balancing and optimization of your site, how to use Security Manager to protect your site, and how to analyze your site traffic. So today we need to involve a lot of content.
Our course is to provide an overview of Windows DNA at a height of 50,000. We will discuss scalability and availability, how to optimize an e-commerce site, how to protect this e-commerce site, and finally how to analyze the traffic of the e-commerce site. We will also discuss UA Plus in this section.
The next slide is the Windows DNA expansion model. You will notice that we have the presentation layer, business logic layer, and data layer. In the expression layer, we have a small number of users, who are your standard Internet users and a large number of users at the customer level of standard Visual Basic or other programming languages.
Note that we need to move from a large number of users to a small number of users, and this action is actually driven by Windows DNA. In the business logic layer, we put all the business problems. In the data layer, we have databases, Legacy systems, and external applications.
So why did we go from a 2-layer system to a 3-layer system? Yes. First, the two-layer system has poor scalability, mainly because of its large script. And it requires a separate server. It has low performance and is not suitable for storing a large amount of code. It does not compress the business logic and is not easy to reuse.
Now let's look at the three-layer model, which is an ASP commercial application. Note that we have three layers. The first layer is ASP and html pages. This is our presentation layer in the latest slide. It includes, usually, your UI (that is, the user interface), some simple data validation, along with ASP and html code.
On the second layer, that is, the middle layer or business logic layer, we have a business target layer. This includes your business rules and it consolidates your data through various resources. It occurs here.
The last layer is the data service layer, which is the data integrity rules. It is important to know that it is not only a database management system, but also functions of the email system and various other external systems, this allows us not to be blocked by various constraints in a layer-2 system.
Here is a commercial application tool that still uses ASP. We now have Internet Information Server. In our active Server page layer, we will now display the scripting language, VB script or Java script, and our active Server page layer, then directly connect to the commercial component layer, which is the VB language, CC Plus or Java.
Next is our last layer-Data Layer. In this example, we use the sequel server. The question that arises is why we need to use layer 3. We have discussed the limitations of a 2-layer system. The layer-3 system is eventually scalable. It can be scaled to various servers, such as a network font library. We can move commercial components to an intermediate layer server. We can also move the data layer to a data server, which allows us to expand and ultimately allow us to protect our systems in a more comprehensive way.