Web Protocol
26 items tagged with "web-protocol"
Patterns3
HATEOAS
Hypermedia as the Engine of Application State: REST responses include links describing available actions, letting clients navigate the API by following links.
API Versioning
Strategies for evolving an API without breaking existing clients, by exposing multiple versions through URLs, headers, or media types.
Webhook
A server pushes event notifications to a client-registered HTTP endpoint as events occur, replacing inefficient polling with real-time callbacks.
Reference Architectures5
WAF and DDoS Edge Protection on Google Cloud
Edge security design combining a web application firewall, DDoS mitigation, and a CDN to protect public applications.
Global Edge and CDN Architecture
Multi-CDN edge design that caches content, runs logic at the edge, and routes users to the nearest healthy origin.
Real-Time Collaboration Application
A web app where many users edit shared documents concurrently, synchronized over WebSockets with conflict-free replicated data.
Edge-Rendered Web Platform
A web app rendered at CDN edge locations using lightweight serverless runtimes for low-latency dynamic pages worldwide.
Headless Commerce on Edge
A composable storefront where a static or edge-rendered front end consumes headless commerce, search, and payment APIs over a CDN.
Comparisons3
PHP vs Node.js
Two popular web backends: PHP powers a huge share of the web with mature frameworks, while Node.js offers event-driven JavaScript across the full stack.
Ruby vs Python
Two expressive, dynamic languages: Ruby is beloved for web development with Rails, while Python dominates data, ML, and general-purpose scripting.
WebSockets vs Server-Sent Events
WebSockets give full-duplex bidirectional channels; Server-Sent Events provide simple one-way server-to-client streaming over HTTP.
Benchmarks4
Core Web Vitals
Google's set of user-centric web performance metrics, LCP, INP, and CLS, that quantify loading, interactivity, and visual stability of real page loads.
Lighthouse Performance
Google's open-source web auditing tool that runs synthetic page loads and produces a 0-100 performance score from lab metrics like LCP, TBT, and CLS.
HTTP/3 and QUIC Protocol Benchmark
Measures how the QUIC-based HTTP/3 transport compares to HTTP/2 over TCP on connection setup, throughput, and latency, especially on lossy networks.
Lighthouse Accessibility Benchmark
Measures a web page's automated accessibility conformance using Lighthouse audits mapped to WCAG, producing a 0-100 accessibility score.
FAQs2
What is CORS and why do I get CORS errors?
Cross-Origin Resource Sharing (CORS) is a browser security mechanism that controls whether a web page can make requests to a different origin (scheme,...
What is the difference between HTTP/2 and HTTP/3?
HTTP/2 introduced multiplexing of multiple requests over a single TCP connection, header compression, and server push, reducing latency compared with ...
Glossaries6
WebSocket
WebSocket is a protocol that provides a persistent, full-duplex communication channel over a single TCP connection, enabling real-time two-way data exchange between client and server.
Server-Sent Events
Server-Sent Events (SSE) is a web standard that lets a server push a continuous, one-way stream of text updates to a client over a single long-lived HTTP connection.
HTTP/2
HTTP/2 is a major revision of the HTTP protocol that adds request multiplexing, header compression, and server push over a single connection to improve web performance.
HTTP/3
HTTP/3 is the third major version of HTTP, running over the QUIC transport on UDP to eliminate transport-level head-of-line blocking and speed up connection setup.
TLS
TLS (Transport Layer Security) is a cryptographic protocol that secures network communication by providing encryption, integrity, and authentication between two parties.
CORS
CORS (Cross-Origin Resource Sharing) is a browser security mechanism that uses HTTP headers to let a server permit web pages from other origins to access its resources.