Advanced Search

Save Or Share This Report

For Application Development & Delivery Professionals

API Design, Part 1: REST Is The Leading But Not Only Option For Your APIs

Favor Pragmatic REST Over REST Theory; Use SOAP And MOM Where Appropriate

August 21, 2013

Primary author headshot

Authors

Why Read This Report

To fully exploit the business opportunity available through application programming interfaces (APIs), your designers must consider each API's purpose and audience as they answer a wide range of technical design questions. Although open Web APIs heavily favor REST messaging, the data shows that SOAP and messaging queuing can provide certain benefits, particularly for B2B APIs and internal APIs. As part of a series on API design practices, this report examines industry data and directions for positioning REST within your API strategy and for overall guidance on REST API design.

Get Access

Already a Client?

Log in to read this document.

Become a Forrester Client

Customers are the new market-makers, reshaping industries and changing how businesses compete and win. Success depends on how well and how fast you respond. Forrester Research gives you insights and frameworks aligned to your role to shorten the time between a great idea and a great outcome, helping your teams win in the age of the customer. Contact us to learn more.

Purchase Report

This report is available for individual purchase ($499 USD).

Purchase

Table of Contents

  • Let Business Opportunity Drive Technical Design Of Your APIs
  • Consider Using More Than REST Within Your API Technical Design Scope
  • Design REST APIs Using Pragmatic REST, Not REST Theory
  • RECOMMENDATIONS

  • Incorporate Guidance On REST Into Your API Design Strategy
  • Supplemental Material
  • Related Research Documents

Recommended Research