Document-based WEB and application-based WEB

There are two types of WEB: document type and application type.

Document-type WEB is used to carry content. It doesn’t require much interaction, but it does need to be search engine friendly. For example, various blogs, content, media websites, etc.

Application WEB is used to complete various complex interactive functions. Be interactive, but don’t need to be search engine friendly. For example, SAAS, WEBAPP, mini programs, WEB games, etc. all fall into this category. These application-based WEBs can even be packaged into mobile APPs, PC and MAC applications.

It is very meaningful to distinguish between two types of WEB.

Last year, I developed my own low-code development platform using vue and nuxt framework. Based on the idea of using a unified technology stack for the front end, all the list pages and content pages used to present content are also implemented using vue and nuxt.

Development is really fun. Deployment is just too awkward. The low-code development platform and the corresponding management platform are both SAAS and application-oriented WEB. The part used to present content is the document-type WEB. For a small part of document-based WEB, I had to use nodejs to deploy it, just to be indexed by search engines. It feels like killing a chicken with a knife.

I have never used nodejs before, but I discovered it after using it. Its deployment is much more troublesome than php. Moreover, nodejs consumes several to ten times more server memory than PHP, and the server configuration has to be upgraded.

What's the final result?

The document-based WEB engineered using vue and nuxt front-end is no better than the document-based WEB generated using back-end languages such as php or golang. Instead, it increases costs.

No need.

Document-based WEB is more suitable to be generated directly using the back-end language.