photoncloud-monorepo/flaredb/specs/003-kvs-consistency/research.md
centra 8f94aee1fa Fix R8: Convert submodule gitlinks to regular directories
- Remove gitlinks (160000 mode) for chainfire, flaredb, iam
- Add workspace contents as regular tracked files
- Update flake.nix to use simple paths instead of builtins.fetchGit

This resolves the nix build failure where submodule directories
appeared empty in the nix store.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
2025-12-09 16:51:20 +09:00

684 B

Research: Distributed KVS Consistency Modes (003-kvs-consistency)

Decisions

  • Consistency scope: Namespace-level selection of strong or eventual consistency.

    • Rationale: Different tenants/workloads can choose per requirement.
    • Alternatives considered: Cluster-wide only (too rigid).
  • Eventual consistency conflict resolution: Default LWW (last-write-wins); allow alternative policies via config.

    • Rationale: Simple baseline with deterministic resolution; extensible for advanced policies.
    • Alternatives considered: Version vectors/CRDT as default (more complex to operate by default).

Open Questions

  • None (resolved by spec clarifications).