Table of Contents
Representational state transfer (REST)
Return to SOAP, RESTful, GitHub star ranking for organizations, GitHub star ranking for repositories, GitOps or GitHub
- Snippet from Wikipedia: REST
REST (Representational State Transfer) is a software architectural style that was created in 2000 to guide the development of the World Wide Web.
REST is defined as a set of six constraints for the ideal architecture of a distributed, Internet-scale hypermedia system such as the Web: Client/Server, Stateless, Cache, Uniform Interface, Layered System, and Code on Demand. (See The six constraints, below.)
The motivation for these six constraints is to grant the system desirable properties such as modularity, scalability, latency-reduction, security, and compatibility with legacy systems. (See Implied architectural properties.)
REST has been used to create stateless, reliable, web-based applications. An application that adheres to the REST architectural constraints may be informally described as RESTful, although this term is more commonly associated with the design of HTTP-based APIs and what are widely considered best practices regarding the "commands" (HTTP methods) a resource responds to, while having little to do with REST as originally formulated—and is often even at odds with the concept.
YouTube Videos
Cloud Monk recommends the following YouTube video:
GitHub Tags
External Sites
Main
- rest
Interesting Articles
Support Resources, FAQs, Q&A, Docs, Blogs
Search Engines
Repos and Registries
Package Managers Artifact Registries and Repos:
- https://hub.docker.com/search?q=rest &type=image - Docker Hub Search
Courses
Books
Vidcasts-Podcasts
Cloud Monk is Retired (for now). Buddha with you. Copyright | © 2024 Losang Jinpa or Fair Use. Disclaimers. REPLACE with: navbar_footer