berkaroad/Eventual2PC
43.5
Weak · 8 November 2026
682
lines of production code
C#
primary language
7
measurements over time
What this system is
Eventual2PC is a .NET-based distributed transaction framework designed to coordinate multi-aggregate root interactions using two-phase commit (2PC) and TCC patterns. It provides the core abstractions for transaction initiators and participants, along with domain events and command interfaces to manage pre-commit, commit, and rollback states. The system is structured as a reusable library, packaged as a NuGet package for integration into larger applications.
Features
Initial release of the Eventual2PC framework
The repository is initialized with the core structure for the Eventual2PC library, including a .NET project, a Makefile for building and packing the NuGet package, and a comprehensive README documenting the 2PC/TCC patterns, domain terminology, and processing flows. This establishes the baseline for a distributed transaction framework supporting multi-aggregate root interactions.
(repo-wide) · high confidence
Initial version of the Eventual2PC module
The Eventual2PC module is introduced, providing the foundational interfaces and classes for a two-phase commit (2PC) transaction system. This includes the core abstractions for transaction initiators and participants, along with a comprehensive set of domain events (such as pre-commit success/failure, commit, and rollback events) and corresponding command interfaces to facilitate distributed transaction coordination.
src/Eventual2PC · 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
Score
- CAI 44 → 43 (-0.1)
- Rubric changed (rubric-2026.10.5 → rubric-2026.11.2) — scores are not directly comparable.
Lenses
- Code Health 100 → 100 (+0.0)
- Architecture 69 → 69 (+0.0)
- Maturity 51 → 48 (-2.6)
- Readiness 19 → 19 (+0.0)
- Security 100 → 100 (+0.0)
- Performance 70 → 77 (+7.4)
Resolved (4)
- Inconsistent use of 'Succeed' vs 'Success' and 'Failed' vs 'Failure' across types and methods. The type ITransactionParticipantPreCommitSucceed uses the verb form 'Succeed', while the method AddPreCommitSuccessParticipant uses the noun 'Success'. Similarly, the type ITransactionParticipantPreCommitFailed uses the adjective 'Failed', while the method AddPreCommitFailedParticipant also uses 'Failed'. This creates a mismatch between the event type names and the command/actor method names. The convention should be consistent: either all use the verb form (Succeed/Failed is not a verb, so Succeeded/Failed) or all use the noun form (Success/Failure).
- The concept of a participant successfully completing the pre-commit phase is named inconsistently. One method uses 'PreCommitFailed' (which semantically contradicts 'Success' in the other name, or implies a different state) while the other uses 'PreCommitSuccess'. Given the context of 'Failed' vs 'Success', it is highly likely that 'PreCommitFailed' is a typo for 'PreCommitSucceeded' or vice versa, or that the naming convention for the success state is split between 'Success' and 'Succeeded'. However, looking at the events, we see ITransactionParticipantPreCommitSucceed and ITransactionParticipantPreCommitFailed. The method AddPreCommitFailedParticipant likely corresponds to the failure event, but the existence of AddPreCommitSuccessParticipant alongside AddPreCommitFailedParticipant suggests a symmetry issue where one uses the adjective 'Failed' and the other the noun/verb form 'Success'. More critically, comparing AddPreCommitFailedParticipant with AddPreCommitSuccessParticipant reveals a lack of parallel structure: 'Failed' is an adjective describing the state, 'Success' is a noun. The event interface uses PreCommitSucceed (verb/noun) and PreCommitFailed (adjective). The method names should align with the event names or each other. If the event is PreCommitSucceed, the method should likely be AddPreCommitSucceededParticipant or AddPreCommitSuccessParticipant is acceptable if the event was PreCommitSuccess. But PreCommitFailed vs PreCommitSucceed is the root inconsistency in the domain model naming.
- The property naming for the collection of participants is inconsistent. In the AnyParticipantPreCommitFailed event, the property is named PreCommitSucceedTransactionParticipants, which is semantically confusing (why does a 'Failed' event have 'Succeed' participants?) and structurally different from TransactionParticipants in the AllParticipantPreCommitSucceed event. It is likely that PreCommitSucceedTransactionParticipants is a typo for PreCommitFailedTransactionParticipants or that the naming convention for the collection is not consistent (PreCommitSucceed... vs Transaction...).
- XML-doc coverage: Eventual2PC (src/Eventual2PC/Eventual2PC.csproj)
Written by cca.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.
Survey your own repository
berkaroad/Eventual2PC 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 8 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 c3ba31c71034a5b0157abf39663188e5334b387c — 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-45ab2cab63de.