Javascript-choice between single-page and backend template rendering methods?

Currently, there are two popular development methods: 1. Single-page applications are written through AngularJs, EmberJs, or ReactJs at the front-end, and only data interfaces are provided at the backend. In the backend, there is no difference between front-end pages and mobile apps, the front and back ends are completely separated. Example: Evernote 2: The frontend of backend template rendering is provided to the backend... two popular development methods are available:
1. single page
The front end writes a single-page application through AngularJs, EmberJs, or ReactJs. the back end only provides data interfaces. In the backend, the front-end page is no different from the mobile App, and the front and back ends are completely separated. Example: Evernote

2. backend template Rendering
The front end provides a good page for the backend to write the template engine to render the page. This is a traditional method. In addition to writing the template engine to render the page, the backend also provides an interface for the mobile App separately, the front-end is generally relatively easy to write static pages. For example, most websites, such as segmentfault

The problem arises. If a website was previously rendered by a traditional backend template, and later on the mobile phone end, the backend also provided interfaces to the mobile phone, in order to ensure consistency and backend maintenance costs, is it necessary for me to change my website to a single-page application?

Reply content:

Two Popular development methods are available:
1. single page
The front end writes a single-page application through AngularJs, EmberJs, or ReactJs. the back end only provides data interfaces. In the backend, the front-end page is no different from the mobile App, and the front and back ends are completely separated. Example: Evernote

2. backend template Rendering
The front end provides a good page for the backend to write the template engine to render the page. This is a traditional method. In addition to writing the template engine to render the page, the backend also provides an interface for the mobile App separately, the front-end is generally relatively easy to write static pages. For example, most websites, such as segmentfault

The problem arises. If a website was previously rendered by a traditional backend template, and later on the mobile phone end, the backend also provided interfaces to the mobile phone, in order to ensure consistency and backend maintenance costs, is it necessary for me to change my website to a single-page application?

Make a comparison table for you:

Recruit full-stack development, rendering on the server end on the first screen, interaction on the back, and writing on the front-end js. Based on react, the frontend and backend are unified. The backend is divided into two layers. The outermost layer is also the frontend responsible for node writing, and the other end is the python writing. The part-time DBA is the sauce.

I tried to use node to render the view before. Now I am using angular to render the view. To sum it up, I feel that the latter is more common. As long as the interface is clear, the backend can be connected to anything else, the same is true for the backend. As long as the api is set, the front-end can connect everything.

Low coupling to facilitate secondary development.

It is now a trend. Many things are mobile terminals, WEB, and WAP. Should we write a set of interfaces that can be called by three terminals. This trend is also popular now. The front-end adopts MVC, and the server side removes the view layer and adopts the restful style, focusing on the business logic and processing of data.

It doesn't matter if it's all restful APIs. You can also use node. js for backend rendering. The workload is on your side.

Single-page front-end rendering seo is not easy to do