Our Patterns for API Design, also known as Microservice API Patterns (MAP), capture proven solutions to problems commonly encountered when specifying, implementing and maintaining message-based …

Chapter 1 of the book contains an introduction to API fundamentals and a domain model for APIs. Six architectural decision narratives guide through the conceptual level of API design, identifying 29 …

This article establishes context and scope of MAP, highlights service design challenges, and suggests entry points into the pattern language.

The book features a more extensive cheat sheet for pattern selection in its Appendix A, which also discusses how our patterns relate to ADDR, RDD and DDD. The cheat sheet is ordered chronologically.

Patterns make design knowledge timeless – but concrete and actionable still We mined 44 API design patterns from personal experience and community insights These “Patterns for API Design” support …

Some of our patterns deal with API documentation, while others focus on API building blocks at different levels of abstraction and detail. This page groups patterns by such structural scopes to ease …

In this tutorial, you learn about quality-related patterns for API management and governance and apply patterns that help to choose request and response message sizes.

If you look for concrete guidance how to explore our site and apply the patterns, try one of our tutorials. They mix website/pattern exploration activities with actual API design tasks.

In this tutorial you apply our patterns to design and improve an API in a realistic sample system landscape in five steps: identification, responsibility, structure, quality, and evolution.

Our microservice design patterns can be grouped by lifecycle phase, level of abstraction and refinement, and type of design concern. Each of the resulting categories investigates a set of related design issues.