Trends Report

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 21st, 2013
Randy Heffner, null
Randy Heffner
With contributors:
Mike Gilpin , Michael Facemire , Eve Maler , Steven Kesler


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.

Want to read the full report?

Contact us to become a client

This report is available for individual purchase ($1495).

Forrester helps business and technology leaders use customer obsession to accelerate growth. That means empowering you to put the customer at the center of everything you do: your leadership strategy, and operations. Becoming a customer-obsessed organization requires change — it requires being bold. We give business and technology leaders the confidence to put bold into action, shaping and guiding how to navigate today's unprecedented change in order to succeed.