Resource-oriented architecture
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 resources with "RESTful" interfaces. These resources are software components (discrete pieces of code and/or data structures) which can be reused for different purposes. ROA design principles and guidelines are used during the phases of software development and system integration.
- Comment
- enIn 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 resources with "RESTful" interfaces. These resources are software components (discrete pieces of code and/or data structures) which can be reused for different purposes. ROA design principles and guidelines are used during the phases of software development and system integration.
- Has abstract
- enIn 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 resources with "RESTful" interfaces. These resources are software components (discrete pieces of code and/or data structures) which can be reused for different purposes. ROA design principles and guidelines are used during the phases of software development and system integration. REST, or Representational State Transfer, describes a series of architectural constraints that exemplify how the web's design emerged. 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 RPC-style REST architectures are RESTful.
- Hypernym
- Style
- Is primary topic of
- Resource-oriented architecture
- Label
- enResource-oriented architecture
- Link from a Wikipage to an external page
- inspire.jrc.ec.europa.eu/reports/ImplementingRules/network/Resource_orientated_architecture_and_REST.pdf%7Cseries
- archive.org/details/restfulwebservic00rich_0
- Link from a Wikipage to another Wikipage
- API Platform
- Category:Software architecture
- Code reuse
- Data structure
- Django (web framework)
- Flask (web framework)
- Interface (computing)
- JBoss Seam
- Leonard Richardson (video game developer)
- Modular programming
- NetKernel
- O'Reilly Media
- Office for Official Publications of the European Communities
- Play Framework
- Programming paradigm
- Project Jersey
- Remote procedure call
- Representational state transfer
- Roy Fielding
- Ruby on Rails
- Software
- Software architecture
- Software component
- Software development methodology
- Software engineering
- Spring Framework
- Symfony
- System integration
- System resource
- Systems design
- TurboGears
- Web resource
- SameAs
- m.02vq1xw
- Mgo2
- Q13501132
- Subject
- Category:Software architecture
- WasDerivedFrom
- Resource-oriented architecture?oldid=1069489978&ns=0
- WikiPageLength
- 6006
- Wikipage page ID
- 12107449
- Wikipage revision ID
- 1069489978
- WikiPageUsesTemplate
- Template:Cite book
- Template:Dubious
- Template:Reflist
- Template:Sfn
- Template:SfnRef
- Template:Software engineering