In Part 1 of this series, we looked at serverless architecture and what it means for web development. We also looked at Backand and creating an account to work with our to-do List application. In this article, we’ll build our application’s data model by walking through a simple set of requirements. We’ll implement the data model in Backand, then work on building a simple UI to present our data to the user.
Defining Our Requirements
Common software development wisdom is that changing requirements becomes an order of magnitude more challenging as you move through the development process. While a change at design time might have some frustrating repercussions, on average it would cost ten times as much to make the exact same change once design has completed and implementation has begun, and one hundred times as much once development is completed and we’re ready to deploy to production. In recognition of this, let’s spend some time defining the requirements of our application: