REST: Difference between revisions
Line 24: | Line 24: | ||
https://cloud.google.com/apis/design | https://cloud.google.com/apis/design | ||
== Best Practices for Designing a Pragmatic RESTful API by Vinay Sahni == | |||
Best Practices for Designing a Pragmatic RESTful API | Vinay Sahni | |||
https://www.vinaysahni.com/best-practices-for-a-pragmatic-restful-api#restful | |||
== keywords == | == keywords == |
Latest revision as of 00:18, 3 July 2024
REST
"Representational state transfer (REST) is a style of software architecture for distributed systems such as the World Wide Web. REST has emerged as a predominant web API design model." [1]
Clean URL
"Clean URLs, RESTful URLs, user-friendly URLs or SEO-friendly URLs are purely structural URLs that do not contain a query string [e.g., action=delete&id=91] and instead contain only the path of the resource (after the scheme [e.g., http] and the authority [e.g., example.org]). This is often done for aesthetic, usability, or search engine optimization (SEO) purposes. Other reasons for designing a clean URL structure for a website or web service include ensuring that individual web resources remain under the same URL for years, which makes the World Wide Web a more stable and useful system, and to make them memorable, logical, easy to type, human-centric, and long-lived."
Examples of "unclean" versus "clean" URLs follow:
Unclean URL | Clean URL |
---|---|
http://example.com/index.php?page=foo | http://example.com/foo |
References:
- Clean URL - Wikipedia - http://en.wikipedia.org/wiki/Clean_URL
Google API Design Guide
https://cloud.google.com/apis/design
Best Practices for Designing a Pragmatic RESTful API by Vinay Sahni
Best Practices for Designing a Pragmatic RESTful API | Vinay Sahni https://www.vinaysahni.com/best-practices-for-a-pragmatic-restful-api#restful