Enterprise application issues raised by single-page Web applications

Because of the popularity of single-page Web applications, there have been some subtle changes between the client and server side, such as the fact that the client was only used to display pages and clarify logic, and now it has evolved into an application that can enter the drive state.

The future of enterprise application development, as well as the eventual implementation of the technology will certainly have a lot of changes, but the new changes will certainly bring some problems for the development and management personnel, thus triggering a series of technical or practical issues.

If the server side excludes page rendering capabilities ...

1. Reduce the pressure on the server itself. The server side does not save the state content of any client, which increases the processing capacity of the server indirectly.

2. The same server side can accommodate different types of clients, including iOS, Android and browser.

3. When the server needs to switch, the previous practice is to completely push the redo. Now, all the previous pages and interfaces can be reused, greatly reducing the technical cost of the project.

4. Improve efficiency. Page development and server-side development can be carried out at the same time, without creating a tie between each other.

5. Reduce the incidence of avoidable errors. The ability of the rendered page to be excluded from the server side leads directly to the possibility of writing SQL harmonious business logic on the page to 0.

Confusion and doubts from the people in the project ...

After these ideas are thrown out, developers and managers of the project are bound to have many problems, such as:

Twitter has shifted from client side rendering to ServerSide rendering, is it proving that the rendering performance of the server side is better?

Facebook has abandoned HTML5 on the phone, is there some situation?

New things are not tested and certified, concrete practical operation is feasible?

These problems are difficult to explain in a moment, but people are characterized by the reluctance to change the process that they are already familiar with. When a very urgent project is in front of you and there is not enough time to do a full evaluation, then the progress may be a variety of problems, it is only to realize that the previous judgment is wrong. It is also in the face of many such failure experience, it is more incentive we should try some new methods.

Address client and server-side issues in enterprise applications

Many of the comments are on JS crucified, but when you get to know the Angularjs language, you will definitely make a difference. Angularjs can naturally lead us to accept and recognize node, eliminating the very important language barrier and solving the client's performance problem.

Many architects will say that Java has a very mature framework architecture, but the biggest problem now is that Java is used only as a transitional language in the development process. Too many times because a trivial service configuration problem causes the entire web to fail to start, so much so that Java applications should eventually become unified, reducing the cost of doing unit testing.

Enterprise application issues raised by single-page Web applications