chapter sixteen

16 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 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 at 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 publishing the first prototype. In the third part of this book, we continue our journey together with the PetSitter team and application, as they take the next baby steps towards 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, who 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.

16.1 Reviewing the first development sprint

16.2 Planning the next sprint

16.3 Preparing for new features

16.3.1 Reviewing the domain model

16.3.2 Reviewing user stories

16.4 Improving developer experience

16.4.1 Consistency

16.4.2 Error handling

16.4.3 Input validation

16.4.4 Versioning vs. evolvability

16.5 Summary