Actions

Difference between revisions of "Representational State Transfer (REST)"

(Created page with "'''REST''', or '''REpresentational State Transfer''', is an architectural style for providing standards between computer systems on the ...")
 
m
 
Line 1: Line 1:
'''REST''', or '''REpresentational State Transfer''', is an [[Architectural Style|architectural style]] for providing standards between [[Computer|computer]] systems on the [[World Wide Web (WWW)|web]], making it easier for systems to communicate with each other. REST-compliant systems, often called RESTful systems, are characterized by how they are stateless and separate the concerns of client and server.<ref>Definition - What Does Representational State Transfer (REST) Mean? [https://www.codecademy.com/articles/what-is-rest Code Academy]</ref>
+
== What is Representational State Transfer (REST) ==
 +
 
 +
'''Representational State Transfer (REST)''' is a software [[Architectural Style|architectural style]] that defines a set of constraints for designing web services. It is based on the idea of representing the state of a system as a set of resources that can be accessed and modified using standard HTTP methods such as GET, POST, PUT, and DELETE.
 +
 
 +
In a RESTful system, resources are identified using a uniform resource identifier (URI) and can be accessed using standard HTTP methods. The server responds to requests with a representation of the resource in a format such as HTML, XML, or JSON. The client can modify the state of the resource by sending a request with an appropriate HTTP method and a representation of the new state.
 +
 
 +
REST is designed to be simple, scalable, and flexible, and is widely used in web development to create APIs (Application Programming Interfaces) that allow different systems to communicate with each other. It is also used to design web services that can be accessed by a variety of clients, such as web browsers, mobile apps, and other systems.
 +
 
 +
Overall, REST is a widely used and influential software architecture that has shaped the design of many web services and APIs. It is known for its simplicity and flexibility, and is a popular choice for building modern web-based systems.
 +
 
 +
 
 +
 
 +
==See Also==
 +
*[[World Wide Web (WWW)|web]]
 +
 
 +
 
 +
 
 +
 
 +
 
 +
==References==
 +
<references />

Latest revision as of 21:53, 29 December 2022

What is Representational State Transfer (REST)

Representational State Transfer (REST) is a software architectural style that defines a set of constraints for designing web services. It is based on the idea of representing the state of a system as a set of resources that can be accessed and modified using standard HTTP methods such as GET, POST, PUT, and DELETE.

In a RESTful system, resources are identified using a uniform resource identifier (URI) and can be accessed using standard HTTP methods. The server responds to requests with a representation of the resource in a format such as HTML, XML, or JSON. The client can modify the state of the resource by sending a request with an appropriate HTTP method and a representation of the new state.

REST is designed to be simple, scalable, and flexible, and is widely used in web development to create APIs (Application Programming Interfaces) that allow different systems to communicate with each other. It is also used to design web services that can be accessed by a variety of clients, such as web browsers, mobile apps, and other systems.

Overall, REST is a widely used and influential software architecture that has shaped the design of many web services and APIs. It is known for its simplicity and flexibility, and is a popular choice for building modern web-based systems.


See Also



References