Difference between revisions of "Representational state transfer"

From Wiki @ Karl Jones dot com
Jump to: navigation, search
(External links)
 
(5 intermediate revisions by the same user not shown)
Line 2: Line 2:
  
 
REST-compliant web services allow requesting systems to access and manipulate textual representations of web resources using a uniform and predefined set of [[Stateless protocol|stateless]] operations.
 
REST-compliant web services allow requesting systems to access and manipulate textual representations of web resources using a uniform and predefined set of [[Stateless protocol|stateless]] operations.
 +
 +
The term ''REST'' stands for ''representational state transfer''.
  
 
== Description ==
 
== Description ==
Line 18: Line 20:
  
 
* [[Architectural pattern]]
 
* [[Architectural pattern]]
 +
* [[Atomicity, consistency, isolation, durability]] (ACID)
 
* [[Backbone.js]]
 
* [[Backbone.js]]
* [[HTML]]
+
* [[Create, read, update and delete]] (CRUD)
* [[Hypermedia]]
+
* [[Java API for RESTful Web Services]]
 +
* [[Resource-oriented architecture]] (ROA)
 +
* [[Resource-oriented computing]] (ROC)
 
* [[Scalability]]
 
* [[Scalability]]
 +
* [[Semantic URL]]
 +
* [[Service-oriented architecture]] (SOA)
 +
* [[Web-oriented architecture]] (WOA)
 
* [[SOAP]]
 
* [[SOAP]]
 
* [[Software architecture]]
 
* [[Software architecture]]
Line 33: Line 41:
 
* [https://en.wikipedia.org/wiki/Representational_state_transfer Representational state transfer] @ Wikipedia
 
* [https://en.wikipedia.org/wiki/Representational_state_transfer Representational state transfer] @ Wikipedia
 
* [https://en.wikipedia.org/wiki/Overview_of_RESTful_API_Description_Languages Overview of RESTful API Description Languages] @ Wikipedia
 
* [https://en.wikipedia.org/wiki/Overview_of_RESTful_API_Description_Languages Overview of RESTful API Description Languages] @ Wikipedia
 +
* [https://www.kiuwan.com/blog/bad-guys-love-rest/ Bad guys love REST]
 +
* [http://www.vinaysahni.com/best-practices-for-a-pragmatic-restful-api Best Practices for Designing a Pragmatic RESTful API]
 +
* [http://blog.mwaysolutions.com/2014/06/05/10-best-practices-for-better-restful-api/ 10 Best Practices for Better RESTful API]
 +
* [https://blog.philipphauer.de/restful-api-design-best-practices/ RESTful API Design. Best Practices in a Nutshell.]
 +
* [http://blog.octo.com/en/design-a-rest-api/ How to design a REST API]
  
 
[[Category:Computer science]]
 
[[Category:Computer science]]
 
[[Category:Web design and development]]
 
[[Category:Web design and development]]

Latest revision as of 13:39, 3 March 2017

Representational state transfer (REST) or RESTful web services are one way of providing interoperability between computer systems on the Internet.

REST-compliant web services allow requesting systems to access and manipulate textual representations of web resources using a uniform and predefined set of stateless operations.

The term REST stands for representational state transfer.

Description

REST is a coordinated set of constraints applied to the design of components in a distributed hypermedia system that can lead to a more performant and maintainable software architecture.

World Wide Web

The World Wide Web represents the largest implementation of a system conforming to the REST architectural style.

REST has gained widespread acceptance across the Web as a simpler alternative to SOAP and WSDL-based web services.

RESTful systems typically, but not always, communicate over the Hypertext Transfer Protocol with the same HTTP verbs (GET, POST, PUT, DELETE, etc.) used by web browsers to retrieve web pages and send data to remote servers.

See also

External links