Summary

Now, you know that choosing the right API architectural style involves a combination of understanding user personas, business objectives, and technical constraints. You also know how to create a machine-readable definition document for the type of API that you decide to use. Finally, you know the importance of API governance and how applying it to your design and life cycle management processes helps improve your chances of success.

When you began this chapter, you already knew how to define and validate your API design. You took what you had learned and started applying it to creating something concrete, in the shape of a machine-readable API definition. You learned that to pick the right architectural style, you need to connect what you learned from user personas with your business objectives, as well as your technical constraints. Those three criteria help you to evaluate the feasibility of all available API architectural styles and choose the right one. After understanding...