Advanced Search

Save Or Share This Report

For Application Development & Delivery Professionals

API Design, Part 2: Design Messaging Styles By Balancing Reach With Your Other Design Goals

To Foster API Acceptance, Design Around Your API Users' Messaging Preferences And Need For Other Capabilities

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 select messaging types for your API's use and design the details of how you use each messaging type. The core design concerns boil down to balancing reach with other design goals. Simpler forms of REST will reach the broadest open Web API user audience, but SOAP and message queuing can lower the cost of achieving your design goals for B2B APIs and internal APIs. As part of a series on API design practices, this report examines industry data and directions for designing messaging styles using REST, SOAP, MOM, and other special API messaging styles.

Get Access

Already a Client?

Log in to read this document.

Become a Forrester Client

Timely and relevant, Forrester's RoleView research aligns to 13 leadership roles across business and technology management. Our expertise in customer experience, mobile, digital business, and big data will help 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
  • Design Messaging Styles By Balancing Reach With Other Design Goals
  • Alternate API Types Can Provide Strong Reach Within Specific Contexts
  • RECOMMENDATIONS

  • Incorporate Messaging Style Guidance Into Your API Design Strategy
  • Supplemental Material
  • Related Research Documents

Recommended Research