Difference between revisions of "Representational state transfer"
Karl Jones (Talk | contribs) (Remove link, w) |
Karl Jones (Talk | contribs) (Scalability) |
||
| Line 1: | Line 1: | ||
| − | '''Representational State Transfer''' ('''REST''') is a software architecture style consisting of guidelines and best practices for creating [[scalable]] [[Web service|web services]]. | + | '''Representational State Transfer''' ('''REST''') is a software architecture style consisting of guidelines and best practices for creating [[Scalability|scalable]] [[Web service|web services]]. |
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 architecture. | 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 architecture. | ||
Revision as of 10:06, 19 May 2015
Representational State Transfer (REST) is a software architecture style consisting of guidelines and best practices for creating scalable web services.
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 architecture.
REST has gained widespread acceptance across the Web[citation needed] 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.
The World Wide Web represents the largest implementation of a system conforming to the REST architectural style.
External Links
- Representational state transfer @ Wikipedia
- Overview of RESTful API Description Languages @ Wikipedia
