RESTful Node.js: A Structured Approach
  • Book Cover
  • About the Author
  • Links and Resources
  • Part I: The Why
    • Foreword
    • Preface
    • Chapter 1: Introduction
      • The Rise of REST and Distributed Systems
      • Problem #1: Structureless Design, Structureless REST
      • The Emergence of JavaScript and Node.js
      • Problem #2: Structureless JavaScript, Structureless Node.js
      • Behold, the Solution: A Structured Approach
      • Summary
  • Part 2: The Theory
    • Chapter 2: REST Origins
      • A Brief History of the Web and the Birth of REST
      • REST vs. HTTP
      • REST - The Abstract Web Architecture
      • HTTP - A Peak at REST's Concrete Implementation
      • What does it mean for an API to be RESTful?
      • Measuring "RESTfulness" with Richardson Maturity Model
      • Pragmatic REST vs Dogmatic REST
      • Summary
    • Chapter 3: RESTful API Design Guidelines and "Best Practices"
      • Theories vs. Principles vs. Guidelines
      • URI Design
      • Method Verbs
      • Status Codes
      • Representational Design
      • Metadata Design
      • Versioning Strategies
      • Security Considerations
      • Documentation
      • Case Study: GitHub
      • Summary
    • Chapter 4: Structured JavaScript Architecture
      • The Monstrous Monolith and Its Downfall
      • Layered/N-Tier Architecture: The Unpopular Proven Way
      • Microservices and Distributed Computing: A Popular Misdirection
      • Summary
    • Chapter 5: The 8 Step Recipe
      • Route Name (URI)
      • Input Request
      • Middleware
      • Validation
      • Domain
      • Events
      • Output Response
      • Test, Refactor, Document
      • Summary
  • Part 3: The Code
    • Chapter 6: Introduction to the Bookstore API
      • The Bookstore API Endpoint Specifications
      • API Design and Code Structure
      • Project Setup
      • Summary
    • Chapter 7: Retrieving Books from our API
      • Retrieving All Books - Planning
      • Retrieving All Books - Implementation
      • Retrieving A Book By ID - Planning
      • Retrieving A Book By ID - Implementation
      • Summary
    • Chapter 8: Adding Authentication to our API
      • Registering the User - Planning
      • Registering the User - Implementation
      • Logging the User In - Planning
      • Logging the User In - Implementation
      • Getting Authenticated User - Planning
      • Getting Authenticated User - Implementation
      • Summary
    • Chapter 9: Adding the Create, Update, and Delete Operations to our API
      • Creating A Book Listing - Planning
      • Creating A Book Listing - Implementation
      • Updating A Book Listing By ID - Planning
      • Updating A Book Listing By ID - Implementation
      • Deleting A Book Listing By ID - Planning
      • Deleting A Book Listing By ID - Implementation
      • Summary
    • Chapter 10: Testing our API
      • Testing the Request
      • Testing the Middleware
      • Testing the Validation
      • Testing the Domain
      • Testing the Event
      • Testing the Response
      • Testing the Controller
      • Integration Test
      • Summary
  • Conclusion
    • Final Words
  • Bonus!
    • Refactoring to HATEOAS
  • Appendix
    • Sources & References
Powered by GitBook
On this page
Edit on GitHub
  1. Part I: The Why
  2. Chapter 1: Introduction

The Rise of REST and Distributed Systems

PreviousChapter 1: IntroductionNextProblem #1: Structureless Design, Structureless REST

Last updated 3 years ago

The concept of an API predates even the advent of personal computing, let alone the Web, by a very long time! The principle of a well-documented set of publicly addressable "entry points" that allow an application to interact with another system has been an essential part of software development since the earliest days of utility data processing. However, the advent of distributed systems, and then the web itself, has seen the importance and utility of these same basic concepts increase dramatically.

-Martin Bartlett

According to , the first web API was introduced by on February 7th, 2000. However, that API was not to be made publicly available to the world at the time. Back then, Salesforce launched its web-based sales force automation as an "Internet as a service", and XML APIs became part of salesforce.com from day one. The main role of these APIs was for customers to share data across their different business platforms and applications.

The salesforce.com website back in 2000.

Then on July 16, 2002, Amazon launched Amazon.com Web Services allowing developers to incorporate Amazon.com's content and features into their own web sites. Amazon.com Web Services allowed third party sites to search and display products from Amazon.com in an XML format.

Since then, companies such as Flickr, Facebook, and Twitter followed suit and have all released their own publicly available web APIs.

Meanwhile, during the same year, about 9 months later, launched the eBay Application Program Interface (API), along with the eBay Developers Program, making eBay’s APIs openly available for anyone to use. Therefore, both Salesforce and eBay are often regarded as the pioneering companies who introduced the first ever public APIs to the world.

The ebay.com website back in 2001.

According to , there are over 25,000 RESTful APIs open to the public. As you can imagine, RESTful Web APIs have become extremely popular and are nowadays the defacto standard for communication across different systems and transportation of data over the web.

eBay
ProgrammableWeb.com
apievangelist.com
Salesforce