Talking about front-end separation practices from. NET to node. JS (by Vczero)

First, the "No Separation" practice

At the end of 11, with WinForm development program, drag control, point button, connect database, do some basic management system; Java JSP can do everything, server-side splicing template, at most use servlet do some business logic, to do the back-end MVC. At that time, with a school innovation team, do some projects, but basically a person behind the front, now think, really "disorganized", back-end MVC is OK, but the front end, basically can only do some simple effect, the space is not small, fortunately, also basically can complete the project.

I call it "no separation" practice, if it is like a person, the development speed is quite fast.

There is no separation practice between the front and back end, from. NET WinForm, of course, you have to say that WinForm has no service side, this I will refer to the separation of the ASP and the Winfrom thinking, or "End & Service" thinking:

In this process, the experience is to understand the backend business more clearly. Why this is WinForm, rather than ASP, there are two main reasons: one is to highlight the "End & Service", where the desktop program is called the PC Client The second reason is that the back-end separation is basically done on the basis of the practice of ASP.

Java EE developed a data analysis system, is a web-side, the first version of the period is basically no front-end separation, the specific performance is as follows.

Second, start to try the front-end separation (WCF-based front-end separation practices)

At the end of 12, followed by the doctor to participate in the competition, the first real to try to separate the front and back, think of the previous program and maintainability is really food. The game is about a product, not the platform you choose. Because I learned about Java and developed projects in the group, mostly learned. NET, in order to balance, I chose. Net. This time the front-end separation is the deepest, the entire backend architecture begins a new attempt. At that time the service was shared everywhere, so I looked for information everywhere, and then I saw the restful design under the guidance of the Doctor. So the final option is . NET WCF REST + MongoDB build service side, front end is HTML + CSS + JS + Jquery (at that time the front end is not used MVC), server when IIS.

Our project name is "based on XXXX Service", later, the results are good, took a good result. I think the practice of WCF is quite cool, and later in the senior company internship also made a point of WCF services. Specific practices such as:

The whole project is not elaborate, mainly to say the separation of practice, affixed to the work of the development at that time (left: service platform; Right: Micro travel recommended application, are competition research projects):

Thinking: WinForm Why not use this way?

In essence, I think the desktop program is a PC client, but also one of the clients, then you can adopt the way WCF provides services, so if the project is large, part of the focus on service development, part of focus on client development (including PC && Web), So the service can be shared, the client can be all kinds.

Three, the most exciting practice (using node. js as the service middle tier)

I have been working on node. JS for 2-3 years now, at least until I come to work on the product development. node. JS has excellent performance on the server side, especially in IO. Chatting with colleagues at the Android platform yesterday, he said that node. JS adds vitality to the app and improves the overall app experience. Of course, some of the products that have been developed by node. JS are more deeply understood in this way.

The advantage of node. js as an intermediary service, as shown (hehe: The company's products are not mapped, this represents my personal view).

Iv. Summary

(1) "Service platform", multi-call, whether it is PC Client, PC Web, WebAPP, APP (Android && iOS) ...

(2) Focus on the front-end separation practice, play the client's performance and function, the regular PC Web MVC.

(3) Using node. js as the service middle tier to play the performance advantage of event-based and asynchronous Io, at least, some of the services that are written are still pretty good (of course, this is node's credit).

Talking about front-end separation practices from. NET to node. JS (by Vczero)