aditimishra541/event-sourcing-cqrs-examples

This is a core banking service built on the Dropwizard framework, designed to manage client and account data using an event-sourced domain model. It provides a RESTful API for account operations such as deposits and withdrawals, alongside read models for transactions and client lists. The system is supported by comprehensive test coverage and modernized build configurations.

The banking service is introduced with a complete domain model for accounts and clients, including event sourcing infrastructure (EventStore, Aggregate base class) and in-memory persistence. The API exposes resources for managing clients and accounts (open, deposit, withdraw) and provides read models for account transactions and client account lists, all wired through a Dropwizard application bootstrap.

src/main · high confidence

Added unit and integration tests for domain models (Aggregate, Account, Client, Email), exception mappers, the event store, projections, and the retry mechanism. Integration tests verify the full HTTP API for clients, accounts, deposits, withdrawals, and health checks, ensuring the application starts and responds correctly.

src/test · high confidence

The project's build configuration (pom.xml) has been updated to use newer versions of key libraries, including Dropwizard 2.0.9, JUnit 5.6.2, Guava 29.0-jre, and Commons Lang3 3.10. Additionally, the Java target version was raised to 12, and build tooling was enhanced with Error Prone, Checkstyle, and Enforcer plugins.

(dependencies) · high confidence

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

• CAI 60 → 62 (+2.1)
• Rubric changed (rubric-2026.08.19 → rubric-2026.09.15) — scores are not directly comparable.

• Code Health 100 → 99 (-0.6)
• Architecture 69 → 69 (+0.0)
• Maturity 57 → 57 (+0.0)
• Readiness 50 → 54 (+4.5)
• Security 80 → 86 (+6.2)
• Domain Modelling 100 → 89 (-10.6)

• Coverage not included — suite not readable by the collector
• Dependency hygiene not measured — dependency manifest found but not parsed for hygiene
• High: security finding (details withheld)
• High: security finding (details withheld)
• High: security finding (details withheld)
• No exposed public API
• Scanner failed to run — not a clean result
• Test reliability not included
• The README does not mention how to build or run the application (starting the application, examples of use), which are critical for new contributors. (README.md)
• dormant codebase — no living knowledge left to concentrate

• Dependency hygiene PARTLY measured — Maven/Gradle declarations read, no dependency graph resolved
• Documentation: no installation or build instructions (README.md)
• Documentation: no usage examples (README.md)
• Duplicated block (12 lines × 2) (src/main/java/bankservice/service/account/DepositAccountCommand.java)
• Duplicated block (13 lines × 2) (src/main/java/bankservice/domain/model/account/AccountDepositedEvent.java)
• Duplicated block (13 lines × 2) (src/main/java/bankservice/domain/model/client/ClientEnrolledEvent.java)
• High: security finding (details withheld)
• High: security finding (details withheld)
• High: security finding (details withheld)
• High: security finding (details withheld)
• Medium: security finding (details withheld)
• Medium: security finding (details withheld)
• Medium: security finding (details withheld)
• No assertions: retriesGetUpToMaxAttemptsWithoutSharedStateBetweenCalls (src/test/java/bankservice/service/RetrierTest.java)
• No assertions: returnClientAccounts (src/test/java/bankservice/it/ClientAccountsIT.java)
• No dependency advisory monitoring
• Scanner failed to run — not a clean result
• Scanner failed to run — not a clean result
• Workflow token permissions not restricted

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

aditimishra541/event-sourcing-cqrs-examples 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.