vladikk/elastic-event-store

The Elastic Event Store is now available as a fully serverless solution for event sourcing-based systems. This release introduces the core infrastructure, including a DynamoDB table with specific indexes for stream and changeset management, along with Lambda functions for command handling, global indexing, and event publishing. The system supports push subscriptions via SNS FIFO topics for new changesets and events, and pull subscriptions for enumerating global changesets. A statistics endpoint is also provided to monitor stream data.

(repo-wide) · high confidence

The new \src/ees\ package introduces a core event sourcing and analysis engine. It defines command and model structures for managing commit data, stream events, and global indexing. The module includes handlers for versioning, statistics, and fetching changesets and events, along with a DynamoDB infrastructure layer. Key features include optimistic concurrency control via a \ConcurrencyException\, automatic checkpoint calculation for page-based iteration, and the ability to fetch global changesets by checkpoint. The routing logic maps commands to specific handlers, supporting operations like committing events, fetching stream changesets, and assigning global indexes.

src/ees · high confidence

Added src/lambda\_entrypoint.py to serve as the AWS Lambda entrypoint for three distinct functions: request\_handler, publisher, and analysis\_projector. The request\_handler processes incoming events and routes them to the appropriate handler, while the publisher function parses DynamoDB new records and publishes changesets and events to SNS topics. The analysis\_projector function executes the analysis projection engine by fetching global changesets and projecting them to the analysis table. This change encapsulates the integration with Lambda and API Gateway for command processing logic, and moves the DynamoDB implementation to the infrastructure module.

src · medium confidence

Added new handlers in the \src/ees/handlers\ directory to support event sourcing and global indexing capabilities. This includes \CommitHandler\ for managing stream commits with optimistic concurrency control, \GlobalIndexer\ for assigning global indices to changesets, and \AnalysisProjector\ for maintaining global statistics. Additionally, new endpoints are introduced for fetching changesets and events by stream ID, retrieving global changesets by checkpoint, and accessing system statistics and version information.

src/ees/handlers · high confidence

Added new infrastructure modules to handle AWS Lambda event parsing, DynamoDB persistence, and SNS publishing. The \aws\_lambda.py\ module introduces handlers that parse API Gateway and DynamoDB stream events into command objects, including a new statistics endpoint and support for optimistic concurrency management via \expected\_last\_changeset\ and \expected\_last\_event\ parameters. The \dynamodb.py\ module provides a \DynamoDB\ class for storing and retrieving commit data, including methods for fetching stream changesets and events with range filtering. The \sns.py\ module adds an \SNS\ class for publishing messages to FIFO queues, supporting message grouping.

src/ees/infrastructure · high confidence

Added unit tests for the analysis projection engine; Integration tests for stream commit, changeset, and event fetching.

Written by watchdog.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.

• CAI 63 → 64 (+1.2)
• Rubric changed (rubric-2026.08.18 → rubric-2026.09.15) — scores are not directly comparable.

• Code Health 98 → 99 (+0.9)
• Architecture 69 → 66 (-3.1)
• Maturity 68 → 68 (+0.0)
• Readiness 50 → 55 (+5.2)
• Security 94 → 85 (-8.7)

• Coverage not included — suite not readable by the collector
• Dependency hygiene not measured — dependency manifest found but not parsed for hygiene
• Duplicated block (18 lines × 2) (src/ees/infrastructure/aws_lambda.py)
• Duplicated block (20 lines × 2) (src/ees/infrastructure/dynamodb.py)
• Duplicated block (28 lines × 2) (src/ees/infrastructure/dynamodb.py)
• No exposed public API
• Scanner failed to run — not a clean result
• Test reliability not included
• dormant codebase — no living knowledge left to concentrate

• Dependency hygiene PARTLY measured — Python dependencies read, no exact pin to grade for currency
• Documentation: no installation or build instructions (README.md)
• Documentation: no usage examples (README.md)
• Duplicated block (21–23 lines × 2) (src/ees/infrastructure/dynamodb.py)
• Duplicated block (22 lines × 2) (src/ees/infrastructure/aws_lambda.py)
• Duplicated block (46 lines × 2) (src/ees/infrastructure/dynamodb.py)
• High IaC: AWS-0095 (template.yaml)
• High IaC: AWS-0096 (template.yaml)
• High: security finding (details withheld)
• High: security finding (details withheld)
• High: security finding (details withheld)
• High: security finding (details withheld)
• High: security finding (details withheld)
• High: security finding (details withheld)
• High: security finding (details withheld)
• High: security finding (details withheld)
• High: security finding (details withheld)
• High: security finding (details withheld)
• High: security finding (details withheld)
• Low IaC: AWS-0125 (template.yaml)
• …and 10 more

Written by watchdog.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.

vladikk/elastic-event-store 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.