Skip to content
CAI
Software that uses CAICheck a score

yahyanouali/event-sourcing-cqrs-examples

59.3

Adequate · 10 November 2026

1.3k

lines of production code

Java

primary language

9

measurements over time

CAI band scale
CAI trend line
CAI lens gauges

What this system is

This is a Spring Boot-based banking domain application that manages accounts and clients through an event-driven architecture. It exposes RESTful APIs for account and client operations, utilizing an in-memory event store and transaction repository to handle state changes and publish events. The system is built with standard Java libraries and includes comprehensive testing and code quality tooling.

Features

Introduce event-driven banking domain with Spring Boot and in-memory persistence

The application now runs on the Spring Boot framework, replacing previous Java EE technologies. This change introduces a domain model for banking, including Account and Client aggregates that manage state through events (e.g., AccountOpened, ClientEnrolled). The system exposes RESTful APIs for managing accounts (opening, depositing, withdrawing) and clients (enrolling, updating), as well as read models for account transactions and client accounts. An in-memory event store and transaction repository are provided for persistence, supporting optimistic locking and event publishing via a local event bus.

src/main · high confidence

Dependencies

Initial project setup with Spring Boot and updated dependencies

The project has been initialized with a Maven build configuration (pom.xml) based on Spring Boot 2.5.6, establishing the core application structure. This includes dependencies for Spring Boot Actuator and Web, along with testing libraries such as JUnit 5.7.2, Hamcrest 2.2, and Mockito 3.12.4. Additional utility libraries like Guava 30.1.1-jre, Commons Lang3 3.12.0, and Commons Validator 1.7 are included. The build is configured with Maven plugins for checkstyle validation, dependency enforcement, and JaCoCo code coverage, ensuring code quality and test coverage standards are met from the start.

(dependencies) · 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 51 → 59 (+8.7)
  • Rubric changed (rubric-2026.10.5 → rubric-2026.11.2) — scores are not directly comparable.

Lenses

  • Code Health 73 → 73 (+0.0)
  • Architecture 69 → 69 (+0.0)
  • Maturity 51 → 57 (+5.0)
  • Readiness 35 → 52 (+16.4)
  • Security 91 → 86 (-5.0)
  • Domain Modelling 90 → 90 (+0.0)

Resolved (4)

  • Dependency hygiene PARTLY measured — Maven/Gradle declarations read, no dependency graph resolved
  • Documentation: no installation or build instructions (README.md)
  • Medium CVE: [GHSA redacted] (pom.xml)
  • No tests found

New (101)

  • Critical CVE: [GHSA redacted] (pom.xml)
  • Critical CVE: [GHSA redacted] (pom.xml)
  • Critical CVE: [GHSA redacted] (pom.xml)
  • Critical CVE: [GHSA redacted] (pom.xml)
  • Critical CVE: [GHSA redacted] (pom.xml)
  • Critical CVE: [GHSA redacted] (pom.xml)
  • High CVE: [GHSA redacted] (pom.xml)
  • High CVE: [GHSA redacted] (pom.xml)
  • High CVE: [GHSA redacted] (pom.xml)
  • High CVE: [GHSA redacted] (pom.xml)
  • High CVE: [GHSA redacted] (pom.xml)
  • High CVE: [GHSA redacted] (pom.xml)
  • High CVE: [GHSA redacted] (pom.xml)
  • High CVE: [GHSA redacted] (pom.xml)
  • High CVE: [GHSA redacted] (pom.xml)
  • High CVE: [GHSA redacted] (pom.xml)
  • High CVE: [GHSA redacted] (pom.xml)
  • High CVE: [GHSA redacted] (pom.xml)
  • High CVE: [GHSA redacted] (pom.xml)
  • High CVE: [GHSA redacted] (pom.xml)
  • …and 81 more

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

Survey your own repository

yahyanouali/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.

About this page

  • The score is its most recent published measurement, taken on 10 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 ab1ab049bf5618f0e90349a7484675a0dc04a10b — 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.4+preprod-464a0040a931.