Though it still needs to be thoroughly tested, which will be addressed in Chapter 14, Testing Data Persistence, preliminary testing of the JSON-based data file persistence feels pretty solid at this point. The CRUD operations that are required by BaseDataObject, passing through JSONFileDataObject to all of the concrete data objects, are all present and accounted for, and they appear to be fully functional. The change to the structure of the Order class might be cause for some concern with respect to the original design, but was not difficult to deal with. That change should be specifically called out during the approval process for the iteration, since it represents a change to the original design, but it doesn't feel like it will be a cause for any major concerns at this time.

With one data persistence mechanism done, and while the concepts are still fresh, it's time to look at the equivalent processes, backed by a real database engine, for the Central Office applications and service.