Skip to main content

Server ↔ Software Server/Hardware Server to handle response & serve content

Source: developer.mozilla.org/en

Software Server​

Software to control how Client access content hosted on Server

Hardware Server​

Hardware to host server (ie rent via datacenter)

Static Web Server​

Computer Hardware run HTTP Server Software to send Static Content hosted files to Clients

Dynamic Web Server​

Static Web Server with extra Software to update/generate Dynamic Content to send Client

Client​

user to access Server

Database

Proxy​

Server to intermediate client-server connection

Edge​

Buzzword for Server to deploy closer to Client.

Horizontal Scaling​

to add more Hardware Server instances to distribute load across more nodes

Vertical Scaling​

to add more Hardware to existing Server to increase compute 🗼

References​

  1. Client ↔ user to access Server

  2. Software Server ↔ Software to control how Client access content hosted on Server

  3. AJAX ↔ (process) to Asynchronous Data Fetch from Server (via clunky legacy XHR methods)

  4. Thin Client ↔ Browser Client only req to display (pre-rendered) static content from Server

  5. Proxy ↔ Server to intermediate client-server connection

  6. PATH ↔ URL Path on Server

  7. Port ↔ Gate to access Resource on Server

  8. Resource Path ↔ rest of URL after Domain || Path to resource on Server

  9. URL Parameter ↔ Extra placeholder data (as key/value pairs) in URL Segment to query Server

  10. CommonJS ↔ (legacy) Module format (originally) for Servers (Node.js)

  11. WebSockets ↔ Web API to open 2-way Client/Server connection, to push update vs Polling

  12. ws ↔ Node.js Module to build WebSockets Server

  13. Server Side Render ↔ to Pre-render Static Content on Server Backend & serve to Thin Client with each request

  14. Data Fetch ↔ (process) to Async GET data from Server

  15. Status Code ↔ (standard) 3-digit HTTP Response code sent by Server

  16. DDoS ↔ attack to flood Server with wasteful reqs to disrupt legitimate access, often via Botnet

  17. Edge ↔ Buzzword for Server to deploy closer to Client.

  18. DELETE ↔ to send Request to delete Resource on Server

  19. Web Site ↔ collection of Web Pages, access via common Server-hosted Domain Name

  20. Tracker ↔ central Server to track/Announce Seed/Peer list

  21. ETIMEOUT ↔ Error TIMEOUT when unable to connect Server

  22. Server Latency ↔ Latency for Server to process & send back response, includes disk latency

  23. NGINX ↔ Backend Server gateway to Web, Reverse Proxy to handle Requests/Cache/load balance

  24. Vertical Scaling ↔ to add more Hardware to existing Server to increase compute 🗼

  25. socket.io ↔ Node.js Module to build WebSockets with built-in Server/Client & fallback Long Polling

  26. TTFB ↔ Time To First Byte - Server/CDN Latency to send first byte to Client