3 Types of API Fragment Design Strategies

Learn the three API fragment design strategies to accelerate development and ensure consistency across projects.

Learn why we are the Leaders in API management and iPaaS

Diagram about the lifecycle of an application building block, with a focus on the first stage: design.
Pyramind diagram about design strategies with API fragments. The bottom layer contains the Commons and Security fragments. The middle layer contains the Domain fragments. And the top layer is the actual RAML specification, will extend the underlying API fragments.
Screenshot of RAML fragment files organized by two sections: collection and member. Within each section, files are organized based on the method or action.
Screenshot of RAML fragment files organized by two sections: collection and member. Within each section, files are organized based on the method or action.
Screenshot of RAML fragment files organized by two sections: collection and member. Within each section, files are organized based on the method or action.
Screenshot of a RAML library that contains a generic collection of reusable RAML resource types and traits
Screenshot of how to set Client-ID enforcement properties.
Screenshot of how to set OAuth 2.0 properties.
Screenshot of the root file where the Commons fragment is set as a library in order to expose common security schemes to set up on a MuleSoft application.
Screenshot of a centralized library of data types for all CRM integrations (CRM as a back-end service).
Screenshot of Commons, CRM Domain, and Security API Specification Fragments.
Screenshot of import of API fragments as Exchange Dependencies.
Screenshot of how to set up a CRM Customer System API RAML Specification using reusable API fragments.
+

Esta página está disponible en español

Ver en español