We analyze the arguments for using a combined architecture and compare them to the benefits of moving to the new model provided by Core Data 2016. You should be able to make a decision if the new persistent container is for you.
- View Offline
- [Instructor] Before we look at the benefits…of the combined architecture,…let's get familiar with the model.…Here we have two coordinators.…We have, on the right side, a process…with a lot of child and grandchild contexts…and that persisting context is on the background thread.…On the left side, you have a batch worker context…which is used for large bulk imports.…Let's look at the benefits of this model.…Positives are it's really performant with bulk inserts,…and again we get a multi-read/single write process.…
I put a star by there because the multi-read…is limited to the number of coordinators.…Now, the negatives are, that we're still…blocked during the write process…and this is much more complex of a merging process.…In fact, the complexity increases…with child contexts and grandchild contexts.…The complexity is also multiplied…by the number of coordinators.…This is much more complex, we have to manage…not only the coordinator merges,…but also the auto merges from the child contexts…and then those of the grandchild contexts.…
This course is meant for the enterprise developer who wants to get up to speed with the latest methods with Core Data. Instructor Jon Bott starts with a review of the basics, explaining the different architectural data models currently in use, the issues that can arise from these different models, and how the latest changes in Core Data 2016 simplify these models. He wraps up with hands-on migration to the new APIs and further tips on leveraging them in iOS 10 and macOS 10.12 apps.
- Fetching data
- Working with objects, queues, and threads
- Understanding the architectural models
- Managing local and server-side data
- Understanding iOS 10 and macOS 10.12 updates to Core Data
- Migrating to the new core data