Two different Web Applications

After the Torch said today that the donews blog will replace WordPress, Ling Hu raised a technical question. We have discussed this:

Ling HU: I don't care about WP, but I think some people (maybe including me) should reflect on the concept of "Web application.

Birds of prey: There are many Web Applications

Ling HU: first, think about the benefits of Java and. net. One of the biggest benefits is separating the UI, business, and storage from the infrastructure and specific applications. The advantage of this separation is that it facilitates the development of complex business logic and makes adjustments to the UI and storage without modifying the logic.

Mengbird: this is the difference between enterprise applications and Internet applications.

Ling HU: Now the problem is that enterprise applications, without a doubt, need to solve these complicated logics. But what about Internet-based applications? Are they really complicated?

Mengpoultry: in enterprise applications, the persistence and UI layers are relatively thin, while the logic layer is the heaviest. However, Internet applications are characterized by the heaviest UI Layer and the thin logic layer. In most cases, the logic of Internet applications can be distributed to persistence and UI. On the other hand, the two applications face different user groups. Enterprise applications have a limited number of users, but are frequently operated. There are a large number of Internet application users, but there are not many operations.

Ling HU: Yes. This is why Ajax is popular in Internet applications, and many javaer do not agree with it. (The author of webwork thinks Ajax is useless)

Record: Yes. The advantage of AJAX is that it greatly improves the UI development capability, which is of little use for enterprise applications.

Ling HU: Yes. Therefore, the choice of Quixote frameworks like Douban is very mature. For an Internet application, performance is a very important aspect. However, it is not that important to separate pages. In many cases, after the real business logic is stripped out, we may find that there are not many things (for example, Douban, in fact, all of them are queries and then queries ), for this reason, it is not cost-effective to use good hierarchical separation, which leads to performance degradation. I couldn't figure it out before, but now I figured it out.