DatumPersistence class abstract

Abstract interface for persistent storage of Datum sync metadata and configuration.

This interface provides a unified way to store and retrieve sync-related data across different storage backends (Hive, SharedPreferences, SQLite, etc.). It supports both synchronous and asynchronous operations, as well as streaming for real-time updates.

Usage

By default, Datum uses an in-memory persistence layer. To use persistent storage, implement this interface and pass it to Datum.initialize:

// Custom implementation (e.g., Hive, SharedPreferences, SQLite)
class MyPersistence implements DatumPersistence {
  // Implement all required methods...
}

await Datum.initialize(
  config: DatumConfig(...),
  connectivityChecker: MyConnectivityChecker(),
  persistence: MyPersistence(), // Use custom persistence
  registrations: [...],
);

Built-in Implementations

• InMemoryDatumPersistence: Default in-memory storage (data lost on restart)
• HiveDatumPersistence: Hive-based persistent storage (in example app)

Implementations should handle serialization/deserialization of complex objects and provide thread-safe operations where necessary.