SwiftData, Core Data, or GRDB: Choose by the Queries You Actually Run
Framework comparisons for iOS persistence usually line up three model declarations side by side and let the syntax decide. The syntax is the part that matters least.
What decides is the set of operations the data has to support, and whether the product will ask for device sync later.
This article is the second half of a pair. The first, iOS Data Storage: Classify Your Data Before You Choose a Database, works through a travel-planning app called TripBoard and sorts everything it stores into six categories: preferences, secrets, domain entities, user files, disposable cache, and synchronization metadata.
Five of those six were placed without a database at all. Preferences went to UserDefaults, secrets to Keychain, tickets and photos to the file system, thumbnails to a cache the system may delete, and sync state to a handful of fields.
One category was left over: the domain entities. Trips, places, and...
Copyright of this story solely belongs to hackernoon.com. To see the full text click HERE
