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.
blog comments powered by Disqus
Latest Blog Posts
- APIs in DFW
- Adding API Broker Under Monitoring for API Aggregators
- The Dark Matter That Make APIs Work
- Potential for API Aggregators to Provide Valuable Industry Data
- My Talk Tomorrow Night at the Dallas-Forth Worth API Professionals Meetup
- The White House Releases An Open Data Strategy
- When API Success Signals Begin Working Against You
- Get To Know Which Languages Your API Developers Are Using
- Twitters Developer Area is More Embeddable Than API
- Overview Of Backend as a Service (BaaS) White Paper
- Make Sure And Have Multiple KPIs For Your APIs
- API Enabled Toys For Our Children
- I Am Speaking At The Dallas-Forth Worth API Professionals Meetup May 14th
- How Much Do You Spend Attracting and Supporting Freemium API Developers?
- What Does The API Evangelist Do?
- Startups Need To Work Together on API Definitions
- Parse Is Successful By Truly Solving Problems for Mobile Developers
- API Commandment: Thou Shalt Not Forego Talking to a Person
- API Trends
- API Priorities
- Have You Taken A Look At AT&T APis Lately?
- Helping People Understand APIs Through Real World Examples
- Evolving Beyond API Service Providers and Tools to Goal Based API Toolkits
- APIs & The Federal Government
- After Last Couple of Weeks, It's Clear There Is Big Opportunity In The API Space