Question 1

How to migrate from Core Data to RocketData?

Accepted Answer

Review the Core Data comparison docs linked in the README. Start by converting your models to immutable structures and integrating RocketData's consistency manager, but be prepared for a significant architectural shift away from Core Data's object graph.

Question 2

RocketData vs Realm for iOS caching?

Accepted Answer

RocketData focuses on immutable models and custom caching flexibility, while Realm offers a full object database with real-time sync. Choose RocketData for control over cache logic and background processing, Realm for out-of-the-box persistence and simpler setup.

Question 3

Does RocketData work with SwiftUI?

Accepted Answer

Yes, but it requires manual integration with SwiftUI's state management. Use RocketData as a data layer to feed models into SwiftUI views, ensuring updates are handled on background threads to maintain performance.

Question 4

How to implement custom caching with RocketData?

Accepted Answer

Define a cache conforming to RocketData's protocols, such as using NSCache or a third-party key-value store, and configure it for LRU eviction as per the 'Bring Your Own Cache' guidance in the documentation.

Question 5

What are the performance benefits over Core Data?

Accepted Answer

RocketData avoids main-thread blocks and crashes common in Core Data, as stated in the motivation. It scales better with large datasets by processing changes on background threads, reducing UI lag.

Question 6

Can RocketData handle offline data sync?

Accepted Answer

It manages in-memory consistency and caching, but offline sync requires pairing it with a network layer. RocketData ensures local data consistency, but network synchronization logic must be implemented separately.

RocketData

What is RocketData?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Open Source Alternative To

Frequently Asked Questions