API Design Patterns

Web API Design

Craft Interfaces that Designers Love

In most organizations, back-end systems are often based on legacy technologies that have complex interdependencies. It means, they can’t move as quickly as the needs of mobile app developers and keep up with the changing design formats.

Some of the commonly used API design patterns include:

  • The Build Up Approach: developer exposes the core objects of a big system, and puts an XML parsing layer on top. This means, exposing details of internal architecture, which is not feasible.
  • The Standards Committee Approach: Involves using a standards document to define the schema and URLs. This is a slow approach, which may lack adherence.
  • The Copy Cat Approach: involves using somebody else’s API design, thereby missing out on the differentiation part.

Your API needs to be credible, relevant, and differentiated. And, that’s why you need Apigee.

Apigee is the leading solution provider of API technology and products for enterprises and developers. We use the API façade pattern that provides a buffer or virtual layer between the UI on the top, and the API part on the bottom. The API façade pattern provides a comprehensive view from the developer and user perspective.

To learn how to implement an API façade pattern, get the Web API Design guide now.