core-data

To set up the Core Data stack, create an NSPersistentContainer, configure its store descriptions, and load persistent stores to begin managing local data persistence in your application.

Core Data concurrency requires using separate background contexts for multi-threaded data access, ensuring threading rules are followed to prevent race conditions and maintain reliable local storage.

Batch operations in Core Data utilize NSBatchInsert, NSBatchDelete, and NSBatchUpdate to process large data changes efficiently, requiring specific merge guidelines to synchronize changes back into your main context.

Persistent history tracking is needed in Core Data when synchronizing state across multiple targets, allowing you to track and consume incremental changes for reliable local storage consistency.

Core Data supports staged migrations on iOS 17 and later using NSStagedMigrationManager, enabling robust multi-step migration processes and coexistence with composite attributes and SwiftData boundaries.

SwiftData can coexist alongside existing Core Data persistence by applying clear boundary guidance, allowing you to maintain reliable local storage while selectively adopting SwiftData in your app.