Summary
This sample app is far from perfect.
Strategically, this is quite a bit of code for a silly little to-do app. To an extent, the value of formal architectures increases with the size and scope of the app. The more “disposable” the app is, the more likely it is that you can skip some architectural complexity and just focus on writing a working app. As the preceding chapter noted, for smaller apps, YAGNI (You Aren’t Going to Need It).
Tactically, the sample app makes a core simplifying assumption: that the entire set of to-do items fits comfortably in memory. Sometimes that will be the case with full production-grade apps. Sometimes that will not be the case, and the complexity of the app rises.
Prev Table of Contents Next
This book is licensed under the Creative Commons Attribution-ShareAlike 4.0 International license.