j5ik2o/event-store-adapter-rs
57.6
Adequate · 9 November 2026
24.5k
lines of production code
Rust
primary language
7
measurements over time
What this system is
Features
Add tracing infrastructure and conformance data manifest tool
This change introduces tooling to support distributed tracing and standardized conformance testing. It adds a Docker Compose configuration that spins up Jaeger, Zipkin, Prometheus, and the OpenTelemetry Collector, along with their respective configuration files (Prometheus scrape config, OTel Collector pipeline config). Additionally, it includes a Python script (\manifest.py\) to generate and verify SHA-256 checksums for conformance test data files, ensuring data integrity and isolation for memory store tests.
tools · high confidence
Added public API contract verification tool
A new \api-surface/check\ crate has been introduced to validate the library's public API against a defined contract (\surface.json\) and a language-specific mapping (\rs.json\). This tool parses rustdoc JSON output from a fixed nightly toolchain (\nightly-2026-09-27\) and reports deviations in types, methods, and store operations as \Problem\ entries. The \api-surface/fixtures\ crate provides minimal baseline and modified module definitions to support testing this verification logic.
api-surface/check, api-surface/fixtures · high confidence
Initial .takt project configuration and workflow scaffolding
This change introduces the foundational configuration and scaffolding for the .takt directory, establishing the project's operational structure. It adds a .gitignore to manage version control of configuration files (config.yaml, runtime.yaml) and workflow assets while ignoring other content. A new .takt-workflows file points to the upstream takt-workflows repository (version 1760ce095a0ba4aba0b357b08bdf0e65ef910b92) with Japanese language settings. The bin/run-takt.sh script is added to handle launcher logic, including environment variable scrubbing for Claude and Codex accounts, CLI version validation (requiring claude CLI \>= 2.1.280), and mise integration for deterministic tool versions. Configuration in config.yaml defines the project language as Japanese, disables auto-PRs, sets concurrency to 1, and establishes a rate-limit fallback chain switching between Claude (Sonnet 5.5, Opus 5.5), Codex (GPT-6.1-Sol), and OpenCode/Ollama models. Additionally, numerous facet files are added under facets/instructions, facets/knowledge, facets/output-contracts, facets/personas, and facets/policies, including specific DDD (Domain-Driven Design) modeling instructions, knowledge bases for Rust and TypeScript, and review policies, effectively setting up the behavioral and structural rules for the TAKT workflow.
.takt · high confidence
Introduce Bigtable event store backend with token-based authentication
A new Bigtable storage backend is available behind the \bigtable\ feature flag, providing a complete implementation for storing and retrieving event envelopes. This backend supports configurable retention policies (keeping a specific number of snapshots) and enforces strict configuration validation for table layouts and envelope size limits. A key addition is the \BigtableTokenSource\ trait, which allows users to inject a custom access token provider; the library automatically attaches the resulting \authorization: Bearer \<token\>\ metadata to every Bigtable request, handling token retrieval, validation, and error propagation without caching tokens itself.
lib/src · high confidence
Introduce conformance runner for event store adapters
The conformance-runner module has been added to execute the conformance test suite (data version 1.3.0) against event store implementations. It provides a command-line tool that accepts a backend target (memory, DynamoDB, SQLite, or Bigtable) and runs standardized test cases, including fault injection for storage and serialization errors. The runner validates aggregate ID construction, event and snapshot persistence, and retention logic, producing a detailed JSON report of passed, failed, and unverified cases.
conformance-runner · high confidence
Migration CLI now supports migrating from v3 Bigtable and SQLite stores
The migration CLI has been extended to handle v3 data stored in Google Cloud Bigtable and SQLite, in addition to the existing DynamoDB support. Users can now run the \event-store-adapter-migration-rs\ tool to migrate event and snapshot data from legacy Bigtable or SQLite configurations to the new v4 store structure. The CLI automatically detects the target backend based on command-line flags (e.g., \--old-bigtable-\*\ for Bigtable, \--old-sqlite\ for SQLite) and enforces mutual exclusivity between backends. For Bigtable, it supports both production connections using Application Default Credentials and emulator connections for testing. For SQLite, it migrates from a single legacy file to a new v4 SQLite file. All modes support type mapping via a JSON file and provide detailed migration reports.
migration-cli · high confidence
New test utilities for Bigtable, DynamoDB, and ID generation
The test-utils crate now provides helper modules to support testing against Bigtable and DynamoDB backends. It includes a Bigtable admin helper to create tables with specific column families, Docker helpers to spin up LocalStack (for DynamoDB) and the Bigtable emulator, and DynamoDB utilities to create journal and snapshot tables (with TTL enabled for snapshots) and configure a client pointing to a local port. Additionally, a monotonic ULID generator is added to ensure deterministic, ordered IDs across test runs.
test-utils · high confidence
Behavioural changes
1 commit (0 fixes) modifying python
A change to existing behaviour in python — 1 commit, 1 file: “docs: align the user documentation with the hub template and check it in CI (\#339)” (refs \#339).
python · medium confidence · unverified
AI-DLC workflow now supports skipping the operation phase
The AI-DLC adaptive workflow composer has been updated to allow the operation phase to be skipped during workflow composition. This change enables the system to compose minimal viable workflows that stop after the construction phase when the operation stage is not required for the specific task, reducing unnecessary process overhead for tasks that do not need operational planning or deployment configuration.
.claude · medium confidence
Event Store v3: Envelope API replaces traits and enforces opt-in backends
This release introduces a major API overhaul for the event store library. The \Event\ and \Aggregate\ traits have been removed; domain events and aggregates are now plain \serde\ types, with metadata (aggregate ID, sequence number, timestamp) carried by new \EventEnvelope\ and \SnapshotEnvelope\ types. The \EventStore\ API now requires explicit \expected\_version\ for optimistic locking and no longer injects metadata into stored payloads. Additionally, storage backends (DynamoDB, Bigtable, SQLite) are no longer compiled by default; users must explicitly enable them via Cargo features (e.g., \features = \["dynamodb"\]\). Data written by v2 is not readable by v3, requiring manual migration.
(repo-wide) · high confidence
User account example migrated to v3 envelope API
The user-account example has been updated to use the v3 envelope API, where event metadata (aggregate ID, sequence number, timestamp) is carried in envelopes rather than embedded in the domain event or aggregate state. This change introduces explicit optimistic locking via an expected\_version parameter on writes and requires the repository to manage replay positions and versions from the envelope data instead of relying on aggregate fields.
examples/user-account · high confidence
Test coverage
Added integration tests for Bigtable authentication, hooks, migration, and DynamoDB read/migration flows; Added tests for public API surface compliance.
Dependencies
Initial release of event-store-adapter-rs v3.0.2 with multi-backend support
This change introduces the initial version (v3.0.2) of the \event-store-adapter-rs\ library, establishing a Rust workspace that provides event-sourcing adapters for DynamoDB, Google Bigtable, SQLite, and in-memory storage. The library gates backend implementations behind Cargo features (e.g., \dynamodb\, \bigtable\, \sqlite\), requiring users to opt into specific backends. It sets a Minimum Supported Rust Version (MSRV) of 1.94.1 and includes example projects for user-account management using both SQLite and DynamoDB backends.
(dependencies) · high confidence
Housekeeping
AI-DLC workflow artifacts and audit records for SQLite EventStore initiative
This change records the AI-DLC (AI-Driven Lifecycle) workflow artifacts for the SQLite EventStore intent, including reverse-engineering analysis of the existing Rust event-store-adapter library (DynamoDB, Bigtable, Memory backends), code quality assessments, dependency audits, and build/test verification results. It also adds audit logs tracking the workflow stages (initialization, ideation, inception, construction) and state tracking for the 26-stage plan, confirming that the SQLite backend implementation, feature splitting, and Memory backend contract alignment have been generated and verified via local builds and tests.
aidlc · high confidence
Written by cca.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.
How this codebase got here
This is the PUBLIC form of this artifact. Findings are listed in full, but the details of SECURITY findings — which rule fired, in which file, on which line, and how to fix it — are deliberately withheld, and any secret-scanner results are excluded entirely. Where detail is absent here it was REMOVED FOR PUBLICATION; it is not missing from the analysis. The complete artifact is available from the repository owner.
Score
- CAI 58 → 58 (+0.0)
- Rubric changed (rubric-2026.10.5 → rubric-2026.11.2) — scores are not directly comparable.
Lenses
- Code Health 93 → 92 (-0.9)
- Architecture 89 → 89 (-0.3)
- Maturity 47 → 51 (+3.5)
- Readiness 74 → 68 (-6.3)
- Security 48 → 48 (-0.0)
- Performance 100 → 100 (+0.0)
Resolved (5)
- Inconsistent factory method naming and parameter ordering. The Bigtable adapter exposes multiple 'open' variants that differ by optional parameters (token_source, hooks) but lack a unified builder pattern or consistent overloading strategy. Some methods take serializers, others take hooks, some take both, some take neither. This forces users to memorize specific method names for different configuration combinations rather than using a single fluent API.
- Inconsistent factory method naming compared to Bigtable. While similar to Bigtable, the SQLite adapter also suffers from multiple 'open' variants. However, the inconsistency is more pronounced because the Bigtable adapter has 5 open variants while SQLite has 3, and they don't map 1:1 (e.g., Bigtable has 'open_with_token_source' but SQLite does not have an equivalent 'open_with_token_source' method, instead relying on the connection object). This creates confusion when switching between storage backends.
- Inconsistent factory method naming. DynamoDB has 'open_with_serializers' and 'open', but lacks the 'open_with_hooks' variant that Bigtable and SQLite have. This asymmetry makes it difficult to write generic code that works across different storage backends, as the method to inject test hooks or custom serializers varies by implementation.
- Inconsistent factory method naming. Memory adapter uses 'with_serializers' (setter-style) and 'new' (constructor-style), while other adapters use 'open' or 'open_with_*'. This breaks the pattern of using 'open' for initialization across the library.
- Inconsistent method location. 'history_view' is a method on the EventStore implementations (Bigtable, SQLite) but is a method on the underlying Storage (MemoryStorage) rather than the EventStore wrapper. This inconsistency makes it unclear whether history_view is a high-level event store operation or a low-level storage operation, complicating the abstraction layer.
New (22)
- Duplicated block (11 lines × 2) (conformance-runner/src/target_bigtable/scene.rs)
- Duplicated block (12 lines × 2) (lib/src/bigtable/backend.rs)
- Duplicated block (13 lines × 2) (conformance-runner/src/target_bigtable/execute.rs)
- Duplicated block (13 lines × 2) (conformance-runner/src/target_dynamodb/check_requests.rs)
- Duplicated block (21–22 lines × 2) (conformance-runner/src/target_bigtable/execute.rs)
- Duplicated block (22 lines × 2) (conformance-runner/src/target_bigtable/execute.rs)
- Duplicated block (4–7 lines × 3) (conformance-runner/src/target_bigtable/execute.rs)
- Duplicated block (5 lines × 2) (conformance-runner/src/target_bigtable/execute.rs)
- Duplicated block (5 lines × 2) (conformance-runner/src/target_bigtable/execute.rs)
- Duplicated block (5 lines × 2) (lib/src/bigtable/backend.rs)
- Duplicated block (5 lines × 2) (lib/src/spanner/configuration.rs)
- Duplicated block (6 lines × 2) (conformance-runner/src/target_bigtable/emulator.rs)
- Duplicated block (9 lines × 2) (lib/src/bigtable/backend.rs)
- Duplicated block (9–10 lines × 2) (lib/src/spanner/backend.rs)
- FaultPlan::register (cognitive 16) (conformance-runner/src/fault.rs)
- High: security finding (details withheld)
- Hotspot: conformance-runner/src/target_bigtable/execute.rs (conformance-runner/src/target_bigtable/execute.rs)
- event_store_adapter_conformance_rs::target_spanner::execute::run_in_scene (cognitive 33) (conformance-runner/src/target_spanner/execute.rs)
- event_store_adapter_conformance_rs::target_spanner::execute::run_in_scene (cyclomatic 19) (conformance-runner/src/target_spanner/execute.rs)
- event_store_adapter_rs::spanner::configuration::reconcile (cognitive 23) (lib/src/spanner/configuration.rs)
- …and 2 more
Changes since last survey
- 16 commits — 14 feature/other, 2 fixes
By area
- (root) — 7 commits
- lib/Cargo.toml — 4 commits
- conformance-runner/src — 1 commit
- conformance-runner/tests — 1 commit
- lib/src — 1 commit
- lib/tests — 1 commit
- test-utils/Cargo.toml — 1 commit
Notable commits
- fix: fix(deps): testcontainers を astral-tokio-tar 除去後の上流修正に一時固定 (#350)
- fix: fix(test-utils): remove the direct bollard dependency and use the Docker CLI
- change: Disable Renovate bot by setting enabled to false
- change: chore(deny): allow the MIT-0 and Zlib licenses of jsonschema 0.60's dependencies (#347)
- change: chore(deps): Update Rust crate base64 to 0.23.0 (#345)
- change: chore(deps): Update Rust crate jsonschema to v0.58.6 (#266)
- change: chore(deps): Update Rust crate rusqlite to 0.41.0 (#340)
- change: chore: unify the README badges and license as MIT OR Apache-2.0 (#346)
- change: docs: add Rust contributor guide and bilingual design history
- change: docs: align the user documentation with the hub template and check it in CI (#339)
- change: feat: add Spanner storage with v5 conformance (#344)
- change: refactor(test): migrate Docker fixtures from testcontainers to dockertest
- change: test(conformance): run the FNV-1a 64 value cases on the Bigtable leg (#337)
- change: version up to v5.1.0
- change: version up to v5.1.1
- change: version up to v5.2.0
Architecture
- Containers 0 added · 0 removed · contexts 1 added · 0 removed · edges 0 added · 0 removed
Added bounded contexts (1)
- python
Written by cca.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.
Survey your own repository
j5ik2o/event-store-adapter-rs was measured the same way every project in this corpus was: the same rubric, at a pinned commit, with the result published in full. Point a surveyor at a repository you know and see whether you agree with it.
About this page
- The score is its most recent published measurement, taken on 9 November 2026 at a pinned commit. It is not a live figure and does not change until the project is measured again.
- Measured at commit 1d74edcce61cc448502d4f6e03a0c59c0d283f38 — the exact code this score is about.
- Scored under rubric-2026.11.2 — the same rubric and the same method as every other entry in this index.
- Measured by Canine Code Analyzer (cca.canine.dev) using cca measure-2026.11.3+preprod-bb0cb800cd0f.