Posted on 12-12-2011
In my quest to fully understand the underlying principles of Representational State Transfer (REST), i'm re-reading Roy Thomas Fielding original dissertation, Architectural Styles and the Design of Network-based Software Architectures, where he first introduced the REST architectural style.
His dissertation explored the junction of two disciplines in computer science: software and networking.
He identifies that software research:
...has long been concerned with the categorization of software designs and the development of design methodologies, but has rarely been able to objectively evaluate the impact of various design choices on system behavior.
While networking research:
...is focused on the details of generic communication behavior between systems and improving the performance of particular communication techniques, often ignoring the fact that changing the interaction style of an application can have more impact on performance than the communication protocols used for that interaction.
Fieldings work was motivated by the desire to understand and evaluate the architectural design of network-based application software. He wanted to rethink software design in the context of the World Wide Web.
The World Wide Web is intended to be an Internet-scale, distributed system, interconnecting information networks across organizational boundaries, and cope with the demands of scalability and independent deployment of software.
As Fielding states:
REST provides a set of architectural constraints that, when applied as a whole, emphasizes scalability of component interactions, generality of interfaces, independent deployment of components, and intermediary components to reduce interaction latency, enforce security, and encapsulate legacy systems.
As I'm reading his abstract and introduction I can't help but think about where I stand as an API Evangelist, at the convergence of business and RESTful APIs.
When RESTful APIs are applied to business, what does this look like? Is business currently restricted in the same ways as software? When business is operating on the World Wide Web do we need to consider the network more?
Lots to consider at the intersection of business and RESTful APIs.
comments powered by Disqus
Winning in the API Economy
|Download as PDF|
Latest Blog Posts
- I Find It Interesting That Wordnik Created The API Definition Format Swagger
- Autogenerate Runscope-powered API SDKs Using APIMatic
- Where Do We Start With APIs At The University of Oklahoma?
- What I Would Look For When Hiring a Modern API Developer?
- The U.S. International Trade Commission Includes APIs In Latest Report
- Thank You @3Scale For Investing In The Community With @APIStrat
- Introducing API.Report, A Community API News Site
- Extract Knowledge From Audio And Video Using The Clarify API
- My API 101 Workshop At @APIStrat In Chicago Next Week
- Some Advice For The Enterprise When Beginning Your API Journey