Introduction to the history of web server and web technology development

The earliest software all ran on mainframes, and software users log on to the mainframe through "dumb terminals" to run the software. Later, with the rise of PCs, software began to run mainly on the desktop, while software such as the database runs on the server side. This Client/Server model is referred to as the CS architecture.

With the rise of the Internet, people found that the CS architecture is not suitable for the Web. The biggest reason is that the modification and upgrade of web applications are very rapid. The CS architecture requires each client to upgrade the desktop App one by one. Therefore, the Browser/Server model has become popular. , Referred to as BS architecture.

Under the BS architecture, the client only needs a browser, and the logic and data of the application are stored on the server. The browser only needs to request the server, obtain the Web page, and display the Web page to the user.

Of course, Web pages are also highly interactive. Because Web pages are written in HTML, and HTML has super expressive power, and after the server-side upgrade, the client can use the new version without any deployment, so the BS architecture quickly became popular.

Today, in addition to heavyweight software such as Office, Photoshop, etc., most of the software is provided in the form of Web. For example, the news, blog, and Weibo services provided by Sina are all web applications.

Web application development can be said to be the most important part of software development at present. Web development has also gone through several stages:

Static Web page: A text editor directly edits and generates a static HTML page. If you want to modify the content of the Web page, you need to edit the HTML source file again. The early Internet Web pages are static;

CGI: Because static web pages cannot interact with users, for example, a user fills out a registration form, static web pages cannot be processed. To process dynamic data sent by users, Common Gateway Interface, or CGI for short, appeared, written in C/C++.

ASP/JSP/PHP: Because Web applications are characterized by frequent revisions, low-level languages ​​such as C/C++ are not suitable for Web development, and scripting languages ​​have quickly replaced the CGI mode because of their high development efficiency and close integration with HTML. ASP is a Web development technology launched by Microsoft using VBScript script programming, while JSP uses Java to write scripts, and PHP itself is an open source scripting language.

MVC: In order to solve the problem of poor maintainability caused by directly embedding HTML with scripting language, Web applications also introduce the Model-View-Controller mode to simplify Web development. ASP has developed into ASP.Net, JSP and PHP also have a lot of MVC frameworks.

Currently, web development technology is still developing rapidly, and asynchronous development and new MVVM (Vue, Angular) front-end technologies emerge in endlessly.

 

Now the question is: Which MVVM framework is better?

Currently, the commonly used MVVM frameworks are:

Angular : produced by Google, famous, but difficult to use;

Backbone.js : Getting started is very difficult because there are too many APIs;

Ember : A large and comprehensive framework, it is very difficult to write a Hello world.

Our goal in choosing MVVM should be easy to get started, simple to install, able to write JavaScript directly on the page, and expand support when more complex functions are needed.

Therefore, a comprehensive survey, the best option is especially the rain the river MVVM framework for the development of the great God: Vue.js

Guess you like

Origin blog.csdn.net/smilejiasmile/article/details/109385343