Javascript applications

This page explains several concepts of javascript applications.

Javascript environments

Javascript can run in the browser when called from html or run in an interpreter like nodejs, deno or bun.

1 - Browser-app

Browser-app are also called web-app or web-ui.

1.1 - static web app

The easiest app to distribute/install.

1.2 - web-ui with a local server

It runs only locally. It can be used for controlling local system (like robot or admin-tasks).

1.2b - web-ui with a local server as proxy

The local server is used as proxy for communicating with a remote/public server. We fall into the remote/public server concept!

1.3 - web-ui that writes files

Via the local server, the web-ui can read/write local files and therefore store data locally.

1.4 - web-ui communicates via git

The local server manages a git-client and exchanges data with a remote/public git-server. This enables a slow communication with several peers.

1.5 - web-ui with a remote server and git-backend

Classic approach but with a git-backend for more reliability but lower performances.

1.6 - web-ui with a remote server and DB-backend

Classic approach but with a database-backend for more performances.

2 - Nodejs-app

NodeJS lets javascript run as servers, CLI, interactive-shell, scripts and others …

2.1 - node-app using its own embedded data

NodeJS-app can be distributed with companion data. Use npx for such apps.

2.2 - node-app using local data

NodeJS-app reads/writes local data that can then be managed with git. Use npm for such apps to find the file structure easily.

2.3 - node-app using current data

NodeJS-app reads/writes any file-path on the local machine. Use npx for such apps.