If you are familiar with Core Data or Realm, Dflat occupies the same space as these two in your application. It helps you to persist and retrieve objects to or from disk for your application needs. Unlike these two, Dflat has a different set of features and makes very different trade-offs. These features and trade-offs are grounded from real-world experiences in writing some of the world largest apps. Dflat is also built from ground-up using Swift and hopefully, you will find it is natural to interact with in the Swift language.
I've been writing different structured data persistence systems on mobile for the past a few years. Dflat is an accumulation of lessons-learned when building these proprietary systems. On iOS particular, the go-to choice long has been Core Data. It works, and is the internal data persistence mechanism for many system apps.
But when deploying structured data persistence system to hundreds of millions mobile devices, there are certain challenges, both on the intrinsics of how data is persisted, and on a higher-level how the rest of the app interact with such system.
The Dflat codebase is still in a very young stage. However, the underlying principles have been proving successful in other proprietary systems. Dflat implemented the following features in no particular order:
The system returns immutable data objects that can be passed down to other systems (such as your view model generators);
All queries and objects can be observed. Updates will be published through either callbacks or Combine framework;
Mutation can only happen on separate threads that caller has little control over, thus, asynchronously;
Data fetching can happen concurrently and synchronously on any thread by caller's choice;
Strict serializable multi-writer / multi-reader mode is supported but users can choose single-writer (thus, trivially strict serializable) / multi-reader mode if they desire;
Data queries are expressed with Swift code, and will be type-checked by the Swift compiler;
Schema upgrades require no write-access to the underlying database (strict read-only is possible with SQLite 3.22 and above).
Unlike Core Data, Dflat is built from ground-up with Swift. You can express your data model by taking full advantage of the Swift language. Thus, a native support for
enum (sum-type), with type-checked queries and observing with Combine.