Skip to content

Add operational record storage contracts - #9

Draft
bytemaster-0xff wants to merge 4 commits into
masterfrom
feature/operational-record-store
Draft

Add operational record storage contracts#9
bytemaster-0xff wants to merge 4 commits into
masterfrom
feature/operational-record-store

Conversation

@bytemaster-0xff

Copy link
Copy Markdown
Collaborator

Introduces the provider-neutral Core contracts for compact, mutable operational data.

  • IOperationalRecord defines minimal operational identity and organization scope.
  • IOperationalRecordStore<TRecord> defines point get, upsert, batch upsert, and delete behavior.
  • OperationalRecordKey carries logical scope values without exposing Cassandra partitions, shards, tables, or Mongo collections.

This intentionally does not add query, paging, sharding, TTL, or provider implementation concerns to Core. Those belong in CloudStorage once its current refactor settles.

The first intended consumer is current device connectivity/status, while the abstraction is deliberately broad enough for other high-cardinality operational records.

@sonarqubecloud

Copy link
Copy Markdown

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant