Ark Repository Patterns

The Ark ecosystem supports multi-backend database patterns, including BadgerDB, SQLite, and PostgreSQL. It also uses live stores to manage ephemeral state and event channels for reactive updates across services.

You use RepoManager aggregators in arkd to abstract different data storage implementations like BadgerDB or PostgreSQL. This interface centralizes data access, allowing your service to switch backends without changing core logic.

Yes, the Ark go-sdk supports live stores specifically for managing ephemeral state. It also utilizes event channels to provide reactive updates across services like arkd and fulmine.

Use live stores in the Ark protocol when you need to manage ephemeral state that does not require persistent disk storage. For long-term data, use multi-backend database support like BadgerDB, SQLite, or PostgreSQL.

The best way to structure data access across arkd and fulmine is using the ports and adapters pattern. This hexagonal architecture isolates core application logic from specific database implementations, ensuring modular services.