RESTHTTP

REST over HTTP (often shortened to RESTHTTP) refers to using the REST architectural style to build networked services that communicate primarily via the Hypertext Transfer Protocol (HTTP). In this model, resources are identified by uniform resource identifiers (URIs) and are exchanged between client and server through a representation, typically in JSON or XML. The approach emphasizes a stateless, cacheable, and layered system with a uniform interface for interactions.

Core constraints include a resource-based address space, standard HTTP methods, and a separation of concerns between client and server. Clients manipulate resources using verbs such as GET (read), POST (create), PUT (replace), PATCH (partial update), and DELETE (remove). Responses convey status information with HTTP status codes and expose representations via media types. Hypermedia controls (HATEOAS) may guide clients through application state via hyperlinks.

Design considerations include resource naming and URI design, idempotence of methods, and statelessness to improve scalability. Common practices include content negotiation for formats, versioning strategies in the URI or headers, and the use of authentication and authorization tokens (OAuth, JWT) over TLS. RESTful APIs often leverage standard HTTP caching mechanisms to reduce latency and load.

Advantages of RESTHTTP include simplicity, wide tooling, and compatibility with the web's existing infrastructure. Limitations can involve inefficiencies for complex queries or real-time communication and require careful design to avoid under- or over-fetching. REST over HTTP remains a dominant approach for interoperable web services and public APIs.