Handling additional access patterns

Consider any of the applications you have built up until today, no matter how big or small. If you have spent some amount of time in the development cycle of the application, be it in any capacity – as a developer, an architect, or any other engineering or product role – you may know that after the scope of the application is defined and the application is launched, it is highly likely that you may come across users of your app wanting a certain functionality that was not part of the initial scope defined for the app.

In this case, you probably would have gone back to the drawing board, figured out what the new feature request was, whether it should be part of the same application, and if yes, what would be the approximate amount of dev hours it might take, and finally, whether that is worth prioritizing. After all this work, you might need to see what changes may be needed on the database level, if any, and how you may need to add...