CoreData common practice - Do you usually have a struct based data class, as the bridge between your UI layer, and the CoreData data layer?

• core-data

  4 767 0.0 Swift

  Sample code for the objc.io Core Data book

  

Yes. This is the general pattern objc.io uses in their excellent book on Core Data and in the corresponding sample code. It makes it much easier if you want to transition to something like Realm for persistence.

• Insanity

  12 7,534 9.2 Swift

  Meta-programming for Swift, stop writing boilerplate code.

This post has some tips on using Sourcery to help automate the creation of that bridge layer.

• InfluxDB

  www.influxdata.com featured

  Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

  

• CleanArchitectureRxSwift

  1 3,824 0.0 Swift

  Example of Clean Architecture of iOS app using RxSwift

CleanArchitectureRxSwift has a concrete demonstration of how using separate structs can help you use isolate persistence so as to use the same view controller with either Realm or CoreData (that obviously applies to more recent persistence options as well).

• cdt-materials

  1 56 0.0 Swift

  The projects and the materials that accompany the Core Data by Tutorials book

  

The only other one book I've read read on the topic, Learning Core Data for iOS with Swift: A Hands-On Guide to Building Core Data Applications, is even older and I definitely learned a lot more from the objc.io one. Raywenderlich has Core Data by Tutorials, which has been updated for iOS 14, but I have not read that one. Glancing at the repo for that book, it definitely does not appear to be as advanced as the objc.io one.

Suggest a related project