Chapter 3. Designing and Publishing APIs
When you’re working with APIs, there’s a lot to keep in mind. One of the first things you should think about is API readiness. Readiness refers to the process of ensuring that an API is fully prepared for deployment and integration into applications. The ultimate goal of any business organization is to create valuable assets that can be integrated into application networks while maintaining high levels of reliability, security, and performance. Without proper planning and structure, things can quickly become disorganized and chaotic. Therefore, it is important to follow standards from the beginning of the development process to ensure that APIs are cost-effectively developed and utilized.
In Chapter 2, you learned how to create RAML and explored its key concepts. You learned how to define RESTful APIs and to structure your documentation for clarity. But there’s a special piece of the puzzle that we haven’t explored in depth yet: RAML fragments, which are pivotal for efficient API design and maintenance.
In this chapter, you will learn about RAML fragments and their importance in developing scalable APIs. We will guide you through the process of creating and organizing fragments, making them reusable across various projects, and sharing and using them in APIs. Additionally, you’ll learn to enable mocking service for your APIs, as well as how to share APIs internally and on public portals for external access and consumption of API assets. ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access