Resource-oriented architecture - Revision history

SuperMarioMan: Reverted edit by 2402:800:621F:B9D3:8D74:3B52:44EE:D909 (talk) to last version by Uzume

2024-11-06T20:32:46Z

Reverted edit by 2402:800:621F:B9D3:8D74:3B52:44EE:D909 (talk) to last version by Uzume

← Previous revision		Revision as of 20:32, 6 November 2024
Line 4:		Line 4:
	REST, or Representational State Transfer, describes a series of architectural constraints that exemplify how the web's design emerged.<ref name="Fielding-Ch5"/> Various concrete implementations of these ideas have been created throughout time, but it has been difficult to discuss the REST architectural style without blurring the lines between actual software and the architectural principles behind it.		REST, or Representational State Transfer, describes a series of architectural constraints that exemplify how the web's design emerged.<ref name="Fielding-Ch5"/> Various concrete implementations of these ideas have been created throughout time, but it has been difficult to discuss the REST architectural style without blurring the lines between actual software and the architectural principles behind it.

	In Chapter 5 of his thesis, [[Roy Fielding]] documents how the World Wide Web is designed to be constrained by the REST series of limitations. These are still fairly abstract and have been interpreted in various ways in designing new frameworks, systems, and websites. In the past, heated exchanges have been made about whether [[remote procedure call\|RPC]]-style REST architectures are RESTful.<ref name="Fielding-Ch5">Chapter 5 of Fielding's dissertation is [http://www.ics.uci.edu/~fielding/pubs/dissertation/rest_arch_style.htm "Representational State Transfer (REST)"].</ref><ref>{{Citation \|last1=Fielding \|first1=Roy T. \|last2=Taylor \|first2=Richard N. \|date=May 2002 \|title=Principled Design of the Modern Web Architecture\|url=http://www.ics.uci.edu/~taylor-REST-TOIT.pdf \|journal=ACM Transactions on Internet Technology \|volume=2 \|issue=2\|pages=115–150\|doi=10.1145/514183.514185\|issn=1533-5399}</ref>		In Chapter 5 of his thesis, [[Roy Fielding]] documents how the World Wide Web is designed to be constrained by the REST series of limitations. These are still fairly abstract and have been interpreted in various ways in designing new frameworks, systems, and websites. In the past, heated exchanges have been made about whether [[remote procedure call\|RPC]]-style REST architectures are RESTful.<ref name="Fielding-Ch5">Chapter 5 of Fielding's dissertation is [http://www.ics.uci.edu/~fielding/pubs/dissertation/rest_arch_style.htm "Representational State Transfer (REST)"].</ref><ref>{{Citation \|last1=Fielding \|first1=Roy T. \|last2=Taylor \|first2=Richard N. \|date=May 2002 \|title=Principled Design of the Modern Web Architecture\|url=http://www.ics.uci.edu/~taylor/documents/2002-REST-TOIT.pdf \|journal=ACM Transactions on Internet Technology \|volume=2 \|issue=2 \|pages=115–150 \|doi=10.1145/514183.514185\|issn=1533-5399}}</ref>

	== Guidelines for clarification ==		== Guidelines for clarification ==

2402:800:621F:B9D3:8D74:3B52:44EE:D909 at 09:58, 2 November 2024

2024-11-02T09:58:18Z

← Previous revision		Revision as of 09:58, 2 November 2024
Line 4:		Line 4:
	REST, or Representational State Transfer, describes a series of architectural constraints that exemplify how the web's design emerged.<ref name="Fielding-Ch5"/> Various concrete implementations of these ideas have been created throughout time, but it has been difficult to discuss the REST architectural style without blurring the lines between actual software and the architectural principles behind it.		REST, or Representational State Transfer, describes a series of architectural constraints that exemplify how the web's design emerged.<ref name="Fielding-Ch5"/> Various concrete implementations of these ideas have been created throughout time, but it has been difficult to discuss the REST architectural style without blurring the lines between actual software and the architectural principles behind it.

	In Chapter 5 of his thesis, [[Roy Fielding]] documents how the World Wide Web is designed to be constrained by the REST series of limitations. These are still fairly abstract and have been interpreted in various ways in designing new frameworks, systems, and websites. In the past, heated exchanges have been made about whether [[remote procedure call\|RPC]]-style REST architectures are RESTful.<ref name="Fielding-Ch5">Chapter 5 of Fielding's dissertation is [http://www.ics.uci.edu/~fielding/pubs/dissertation/rest_arch_style.htm "Representational State Transfer (REST)"].</ref><ref>{{Citation \|last1=Fielding \|first1=Roy T. \|last2=Taylor \|first2=Richard N. \|date=May 2002 \|title=Principled Design of the Modern Web Architecture\|url=http://www.ics.uci.edu/~taylor~~/documents/2002~~-REST-TOIT.pdf \|journal=ACM Transactions on Internet Technology \|volume=2 \|issue=2 \|pages=115–150 \|doi=10.1145/514183.514185\|issn=1533-5399}}</ref>		In Chapter 5 of his thesis, [[Roy Fielding]] documents how the World Wide Web is designed to be constrained by the REST series of limitations. These are still fairly abstract and have been interpreted in various ways in designing new frameworks, systems, and websites. In the past, heated exchanges have been made about whether [[remote procedure call\|RPC]]-style REST architectures are RESTful.<ref name="Fielding-Ch5">Chapter 5 of Fielding's dissertation is [http://www.ics.uci.edu/~fielding/pubs/dissertation/rest_arch_style.htm "Representational State Transfer (REST)"].</ref><ref>{{Citation \|last1=Fielding \|first1=Roy T. \|last2=Taylor \|first2=Richard N. \|date=May 2002 \|title=Principled Design of the Modern Web Architecture\|url=http://www.ics.uci.edu/~taylor-REST-TOIT.pdf \|journal=ACM Transactions on Internet Technology \|volume=2 \|issue=2\|pages=115–150\|doi=10.1145/514183.514185\|issn=1533-5399}</ref>

	== Guidelines for clarification ==		== Guidelines for clarification ==

Uzume: /* Bibliography */ nav

2024-05-26T19:29:10Z

Bibliography: nav

← Previous revision		Revision as of 19:29, 26 May 2024
Line 56:		Line 56:
	*{{Cite book\|last1 = Lucchi\|first1 = R.\|last2 = Millot\|first2 = M.\|last3 = Elfers\|first3 = C.\|year = 2008\|title = Resource Oriented Architecture and REST\|url = http://inspire.jrc.ec.europa.eu/reports/ImplementingRules/network/Resource_orientated_architecture_and_REST.pdf\|series = Scientific and Technical Research\|location = Luxembourg\|publisher = [[Office for Official Publications of the European Communities]]\|doi = 10.2788/80035\|isbn = 978-92-79-09320-3\|issn = 1018-5593}}		*{{Cite book\|last1 = Lucchi\|first1 = R.\|last2 = Millot\|first2 = M.\|last3 = Elfers\|first3 = C.\|year = 2008\|title = Resource Oriented Architecture and REST\|url = http://inspire.jrc.ec.europa.eu/reports/ImplementingRules/network/Resource_orientated_architecture_and_REST.pdf\|series = Scientific and Technical Research\|location = Luxembourg\|publisher = [[Office for Official Publications of the European Communities]]\|doi = 10.2788/80035\|isbn = 978-92-79-09320-3\|issn = 1018-5593}}

	{{~~Software~~ ~~engineering~~}}		{{Web interfaces}}

	[[Category:Software architecture]]		[[Category:Software architecture]]

Kmcnamee: Added short description

2024-04-16T14:29:05Z

Added short description

← Previous revision		Revision as of 14:29, 16 April 2024
Line 1:		Line 1:
			{{short description\|Architectural pattern in software design}}
	In [[software engineering]], a '''resource-oriented architecture''' ('''ROA''') is a style of [[software architecture]] and [[programming paradigm]] for supportive designing and developing [[software]] in the form of Internetworking of [[System resource\|resources]] with "[[Representational state transfer\|REST]]ful" [[interface (computing)\|interface]]s. These resources are [[software component]]s (discrete [[modular programming\|pieces of code]] and/or [[data structure]]s) which can be [[code reuse\|reused]] for different purposes. ROA [[systems design\|design]] principles and guidelines are used during the phases of [[software development methodology\|software development]] and [[system integration]].		In [[software engineering]], a '''resource-oriented architecture''' ('''ROA''') is a style of [[software architecture]] and [[programming paradigm]] for supportive designing and developing [[software]] in the form of Internetworking of [[System resource\|resources]] with "[[Representational state transfer\|REST]]ful" [[interface (computing)\|interface]]s. These resources are [[software component]]s (discrete [[modular programming\|pieces of code]] and/or [[data structure]]s) which can be [[code reuse\|reused]] for different purposes. ROA [[systems design\|design]] principles and guidelines are used during the phases of [[software development methodology\|software development]] and [[system integration]].

Izno: clean div

2023-01-09T05:00:57Z

clean div

← Previous revision		Revision as of 05:00, 9 January 2023
Line 39:		Line 39:

	== Bibliography ==		== Bibliography ==
	<div class="references-1column">
	* {{cite book		* {{cite book
	\|last1=Richardson		\|last1=Richardson
Line 55:		Line 54:
	}}		}}
	*{{Cite book\|last1 = Lucchi\|first1 = R.\|last2 = Millot\|first2 = M.\|last3 = Elfers\|first3 = C.\|year = 2008\|title = Resource Oriented Architecture and REST\|url = http://inspire.jrc.ec.europa.eu/reports/ImplementingRules/network/Resource_orientated_architecture_and_REST.pdf\|series = Scientific and Technical Research\|location = Luxembourg\|publisher = [[Office for Official Publications of the European Communities]]\|doi = 10.2788/80035\|isbn = 978-92-79-09320-3\|issn = 1018-5593}}		*{{Cite book\|last1 = Lucchi\|first1 = R.\|last2 = Millot\|first2 = M.\|last3 = Elfers\|first3 = C.\|year = 2008\|title = Resource Oriented Architecture and REST\|url = http://inspire.jrc.ec.europa.eu/reports/ImplementingRules/network/Resource_orientated_architecture_and_REST.pdf\|series = Scientific and Technical Research\|location = Luxembourg\|publisher = [[Office for Official Publications of the European Communities]]\|doi = 10.2788/80035\|isbn = 978-92-79-09320-3\|issn = 1018-5593}}
	</div>

	{{Software engineering}}		{{Software engineering}}

WikiCleanerBot: v2.04b - Bot T20 CW#61 - Fix errors for CW project (Reference before punctuation)

2022-02-02T15:41:38Z

v2.04b - Bot T20 CW#61 - Fix errors for CW project (Reference before punctuation)

← Previous revision		Revision as of 15:41, 2 February 2022
Line 6:		Line 6:

	== Guidelines for clarification ==		== Guidelines for clarification ==
	The Resource Oriented Architecture, as documented by [[Leonard Richardson (video game developer)\|Leonard Richardson]] and Sam Ruby in their 2007 book ''RESTful Web Services''{{sfn\|Richardson and Ruby\|2007}}, gives concrete advice on specific technical details. Naming these collections of guidelines "Resource Oriented Architecture" may allow developers to discuss the benefits of an architecture in the context of ROA.		The Resource Oriented Architecture, as documented by [[Leonard Richardson (video game developer)\|Leonard Richardson]] and Sam Ruby in their 2007 book ''RESTful Web Services'',{{sfn\|Richardson and Ruby\|2007}} gives concrete advice on specific technical details. Naming these collections of guidelines "Resource Oriented Architecture" may allow developers to discuss the benefits of an architecture in the context of ROA.

	Some guidelines are already common within the larger REST communities such as: that an application should expose many URIs, one for each resource; and that processing cookies representing IDs in a server-side session is not RESTful.		Some guidelines are already common within the larger REST communities such as: that an application should expose many URIs, one for each resource; and that processing cookies representing IDs in a server-side session is not RESTful.

Yahya Abdal-Aziz: harmonise references to Richardson & Ruby's book

2022-02-01T16:18:38Z

harmonise references to Richardson & Ruby's book

← Previous revision		Revision as of 16:18, 1 February 2022
Line 6:		Line 6:

	== Guidelines for clarification ==		== Guidelines for clarification ==
	The Resource Oriented Architecture as documented by [[Leonard Richardson (video game developer)\|Leonard Richardson]] and Sam Ruby{{sfn\|Richardson and Ruby\|2007}} gives concrete advice on specific technical details. Naming these collections of guidelines "Resource Oriented Architecture" may allow developers to discuss the benefits of an architecture in the context of ROA.		The Resource Oriented Architecture, as documented by [[Leonard Richardson (video game developer)\|Leonard Richardson]] and Sam Ruby in their 2007 book ''RESTful Web Services''{{sfn\|Richardson and Ruby\|2007}}, gives concrete advice on specific technical details. Naming these collections of guidelines "Resource Oriented Architecture" may allow developers to discuss the benefits of an architecture in the context of ROA.

	Some guidelines are already common within the larger REST communities such as that an application should expose many URIs, one for each ~~Resource~~ ~~but~~ cookies representing IDs ~~into~~ a server side session ~~are~~ not RESTful.		Some guidelines are already common within the larger REST communities such as: that an application should expose many URIs, one for each resource; and that processing cookies representing IDs in a server-side session is not RESTful.

	== Existing frameworks ==		== Existing frameworks ==
	Richardson and Ruby's ~~2007~~ ~~book ''RESTful Web Services'' discusses~~ many software frameworks ~~which~~ provide some or many features of the ROA. These include		Richardson and Ruby also discuss many software frameworks that provide some or many features of the ROA. These include
	/db,<ref>{{Cite web\|url=https://www.slashdb.com/\|title=API on the Fly™ - Automatically add REST API to Your Databases\|website=SlashDB}}</ref>		/db,<ref>{{Cite web\|url=https://www.slashdb.com/\|title=API on the Fly™ - Automatically add REST API to Your Databases\|website=SlashDB}}</ref>
	[[Django (web framework)\|Django]],		[[Django (web framework)\|Django]],
Line 32:		Line 32:
	While REST is a set of architectural guidelines applicable to various types of computing infrastructures, Resource Oriented Architecture (ROA) is only coupled with the web. This architecture is therefore useful mostly to businesses that consider the web as the computing/publishing platform of choice.		While REST is a set of architectural guidelines applicable to various types of computing infrastructures, Resource Oriented Architecture (ROA) is only coupled with the web. This architecture is therefore useful mostly to businesses that consider the web as the computing/publishing platform of choice.

	The power of the web seems to mostly reside in its ability to lower the barriers to entry for human users who may not be highly trained in using computing machinery. As such, the web widens the market reach for any business that decides to publish some of its content in electronic format.		The power of the web seems to mostly reside in its ability to lower the barriers to entry for human users who may not be highly trained in using computing machinery.{{dubious\|date=February 2022}} As such, the web widens the market reach for any business that decides to publish some of its content in electronic format.
	On the web, such published content is regarded as a [[web resource]].		On the web, such published content is regarded as a [[web resource]].

Yahya Abdal-Aziz: /* Existing frameworks */ - explain which book is meant by the phrase "RESTful Web Services" here

2022-02-01T16:05:37Z

Existing frameworks: - explain which book is meant by the phrase "RESTful Web Services" here

← Previous revision		Revision as of 16:05, 1 February 2022
Line 11:		Line 11:

	== Existing frameworks ==		== Existing frameworks ==
	RESTful Web Services discusses many software frameworks which provide some or many features of the ROA. These include		Richardson and Ruby's 2007 book ''RESTful Web Services'' discusses many software frameworks which provide some or many features of the ROA. These include
	/db,<ref>{{Cite web\|url=https://www.slashdb.com/\|title=API on the Fly™ - Automatically add REST API to Your Databases\|website=SlashDB}}</ref>		/db,<ref>{{Cite web\|url=https://www.slashdb.com/\|title=API on the Fly™ - Automatically add REST API to Your Databases\|website=SlashDB}}</ref>
	[[Django (web framework)\|Django]],		[[Django (web framework)\|Django]],

WikiCleanerBot: v2.04b - Bot T20 CW#61 - Fix errors for CW project (Reference before punctuation)

2021-05-26T19:03:19Z

v2.04b - Bot T20 CW#61 - Fix errors for CW project (Reference before punctuation)

← Previous revision		Revision as of 19:03, 26 May 2021
Line 19:		Line 19:
	JBoss RESTEasy,<ref>{{Cite web\|url=https://resteasy.github.io/\|title=RESTEasy - JBoss Community\|website=resteasy.github.io}}</ref>		JBoss RESTEasy,<ref>{{Cite web\|url=https://resteasy.github.io/\|title=RESTEasy - JBoss Community\|website=resteasy.github.io}}</ref>
	[[JBoss Seam]],		[[JBoss Seam]],
	[[Spring Framework\|Spring]]<ref>{{Cite web\|url=https://spring.io/guides/tutorials/rest/\|title=Spring REST Tutorial}}</ref>,		[[Spring Framework\|Spring]],<ref>{{Cite web\|url=https://spring.io/guides/tutorials/rest/\|title=Spring REST Tutorial}}</ref>
	Apache Wink,<ref>{{Cite web\|url=http://wink.apache.org/\|title=Index\|website=wink.apache.org}}</ref>		Apache Wink,<ref>{{Cite web\|url=http://wink.apache.org/\|title=Index\|website=wink.apache.org}}</ref>
	[[Project Jersey\|Jersey]],		[[Project Jersey\|Jersey]],

Shuber2: Existing frameworks: Add spring

2021-05-25T09:43:33Z

Existing frameworks: Add spring

← Previous revision		Revision as of 09:43, 25 May 2021
Line 19:		Line 19:
	JBoss RESTEasy,<ref>{{Cite web\|url=https://resteasy.github.io/\|title=RESTEasy - JBoss Community\|website=resteasy.github.io}}</ref>		JBoss RESTEasy,<ref>{{Cite web\|url=https://resteasy.github.io/\|title=RESTEasy - JBoss Community\|website=resteasy.github.io}}</ref>
	[[JBoss Seam]],		[[JBoss Seam]],
			[[Spring Framework\|Spring]]<ref>{{Cite web\|url=https://spring.io/guides/tutorials/rest/\|title=Spring REST Tutorial}}</ref>,
	Apache Wink,<ref>{{Cite web\|url=http://wink.apache.org/\|title=Index\|website=wink.apache.org}}</ref>		Apache Wink,<ref>{{Cite web\|url=http://wink.apache.org/\|title=Index\|website=wink.apache.org}}</ref>
	[[Project Jersey\|Jersey]],		[[Project Jersey\|Jersey]],

← Previous revision		Revision as of 19:03, 26 May 2021
Line 19:		Line 19:
	JBoss RESTEasy,<ref>{{Cite web\|url=https://resteasy.github.io/\|title=RESTEasy - JBoss Community\|website=resteasy.github.io}}</ref>		JBoss RESTEasy,<ref>{{Cite web\|url=https://resteasy.github.io/\|title=RESTEasy - JBoss Community\|website=resteasy.github.io}}</ref>
	[[JBoss Seam]],		[[JBoss Seam]],
	[[Spring Framework\|Spring]]<ref>{{Cite web\|url=https://spring.io/guides/tutorials/rest/\|title=Spring REST Tutorial}}</ref>,		[[Spring Framework\|Spring]],<ref>{{Cite web\|url=https://spring.io/guides/tutorials/rest/\|title=Spring REST Tutorial}}</ref>
	Apache Wink,<ref>{{Cite web\|url=http://wink.apache.org/\|title=Index\|website=wink.apache.org}}</ref>		Apache Wink,<ref>{{Cite web\|url=http://wink.apache.org/\|title=Index\|website=wink.apache.org}}</ref>
	[[Project Jersey\|Jersey]],		[[Project Jersey\|Jersey]],

← Previous revision		Revision as of 09:43, 25 May 2021
Line 19:		Line 19:
	JBoss RESTEasy,<ref>{{Cite web\|url=https://resteasy.github.io/\|title=RESTEasy - JBoss Community\|website=resteasy.github.io}}</ref>		JBoss RESTEasy,<ref>{{Cite web\|url=https://resteasy.github.io/\|title=RESTEasy - JBoss Community\|website=resteasy.github.io}}</ref>
	[[JBoss Seam]],		[[JBoss Seam]],
			[[Spring Framework\|Spring]]<ref>{{Cite web\|url=https://spring.io/guides/tutorials/rest/\|title=Spring REST Tutorial}}</ref>,
	Apache Wink,<ref>{{Cite web\|url=http://wink.apache.org/\|title=Index\|website=wink.apache.org}}</ref>		Apache Wink,<ref>{{Cite web\|url=http://wink.apache.org/\|title=Index\|website=wink.apache.org}}</ref>
	[[Project Jersey\|Jersey]],		[[Project Jersey\|Jersey]],