You're reading from MuleSoft Platform Architect's Guide A practical guide to using Anypoint Platform's capabilities to architect, deliver, and operate APIs

Product type Paperback

Published in Jul 2024

Publisher Packt

ISBN-13 9781805126188

Length 498 pages

Edition 1st Edition

Tools

Catalyst

Concepts

CRM

Authors (2):

Jim Andrews

Jitendra Bafna

View More author details

Table of Contents (21) Chapters

Preface

1. Chapter 1: What is the MuleSoft Platform? FREE CHAPTER

2. Chapter 2: Platform Foundation Components and the Underlying Architecture

3. Chapter 3: Leveraging Catalyst and the MuleSoft Knowledge Hub

4. Chapter 4: An Introduction to Application Networks

5. Chapter 5: Speeding with Accelerators

6. Chapter 6: Aligning Desired Business Outcomes to Functional Requirements

7. Chapter 7: Microservices, Application Networks, EDA, and API-led Design

8. Chapter 8: Non-Functional Requirements Influence in Shaping the API Architecture

9. Chapter 9: Hassle-free Deployment with Anypoint iPaaS (CloudHub 1.0)

10. Chapter 10: Hassle-Free Deployment with Anypoint iPaaS (CloudHub 2.0)

11. Chapter 11: Containerizing the Runtime Plane with Runtime Fabric

12. Chapter 12: Deploying to Your Own Data Center

13. Chapter 13: Government Cloud and the EU Control Plane – Special Considerations

14. Chapter 14: Functional Monitoring, Alerts, and Operation Monitors

15. Chapter 15: Controlling API Sprawl with Universal API Management

16. Chapter 16: Addressing Non-Functional Requirements – from a Thought to an Operation

17. Chapter 17: Prepare for Success

18. Chapter 18: Tackling Tricky Topics

19. Index

Why subscribe?

20. Other Books You May Enjoy

How to prevent API sprawl

It is critical for organizations to prevent API sprawl by adopting API best practices and implementing a clear API governance strategy. The first step in preventing API sprawl is to take inventory of the APIs within the organization, determine which APIs are critical for the business, and retire the APIs that are not in use or required anymore.

Once an inventory of APIs that are essential for the business has been created, you can start defining strategies for preventing API sprawl. The following are strategies that can prevent API sprawl:

Use a single source for API discovery: It is difficult for developers to locate APIs and work out their functionality without a single source of truth. For example, multiple lines of business may create APIs that other teams are unaware of. This will create redundant APIs within the organization, which will reduce the APIs’ reusability within the organization. A centralized platform where all APIs can be...