OP here... accessing the underlying SQLite database is very easy by using Core Data. Compare it with using the SQLite C API directly for one second: As things g

OP here... accessing the underlying SQLite database is very easy by using Core Data. Compare it with using the SQLite C API directly for one second: As things grow you will have more or less the same "problems" with the plain C API when it comes to concurrency. Have a look at FMDB (a popular SQLite wrapper written in Objective-C). You will see a class called FMDatabaseQueue which tries to simplify concurrency with SQLite. It follows the same "pattern" as concurrency typed contexts. So I argue that you have the exact same problems when using Core Data that you have when using the raw C API for SQLite - conceptually. The benefit of using Core Data is a nicer API and other features that you would have to reimplement...