Chapter 2. Prototyping APIs
We want the integrations in this book to be created as part of an application network so other users in the enterprise can find, use, and share the applications. We also want the user story to be captured into an interactive API specification, which will ensure that the API is built for business requirements and is not just an afterthought to service the backend. This approach to asset creation will encourage reuse and drive integration success.
In recent years, spec-driven development has emerged as a significant trend in contemporary business systems. We’ve observed a correlation between spec-driven development and continued success in creating robust, scalable, and successful application networks. Previously, API development was implementation driven, with developers quickly prototyping endpoints without initially considering an API specification. But as the code evolved, it caused a lot of problems due to outdated documentation and specifications. Keeping up with all the layers of software development became increasingly difficult. IT began to grow rapidly, and as a result, the product teams struggled to keep up with the disruptions, leading to a significant backlog.
Spec-driven development allows developers to design specifications. It is a process that enables developers to design a specification first, write code according to the design, and then maintain the specification. MuleSoft, with its tools like Anypoint Platform and Anypoint Exchange, ...
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