15 Designing the next API iteration

 

This chapter covers

  • Planning the next development sprint with the PetSitter team
  • Reviewing and updating the user stories with new functional requirements
  • Aspects of the developer experience that we’ll cover in upcoming chapters

In the second part of the book, we met José and his PetSitter team and joined them as they created a web application from scratch. Their journey started with a whiteboard draft of a domain model, continued with an initial API design phase, went through the implementation with various API changes along the way, and finally ended with the publication of the first prototype. In this, the third part of the book, we’ll continue our journey with the PetSitter application and some of the more advanced aspects of OpenAPI. We’ll follow José and the team as they take their next steps toward domination of the global pet-sitting industry.

Let’s imagine the demonstration of the software went incredibly well, and the application worked as designed. Overeager José immediately decided to start using it in production and posted some jobs where he needed someone to take care of his dog. Then he recruited a few of his previous pet sitters as beta testers for the application, and they willingly applied to the pet-sitting jobs through the new system. Nidhi and Max didn’t want to stop his enthusiasm and made sure that the server kept running smoothly.

15.1 Reviewing the first development sprint

15.2 Planning the next sprint

15.3 Preparing for new features

15.3.1 Reviewing the domain model

15.3.2 Reviewing user stories

15.4 Improving the developer experience

15.4.1 Consistency

15.4.2 Error handling

15.4.3 Input validation

15.4.4 Versioning vs. evolvability

Summary

sitemap