Skip to content
CAI
Software that uses CAICheck a score

SpringBootCourses/cqrs-banking-app

49.7

Weak · 8 November 2026

2.3k

lines of production code

Java

primary language

7

measurements over time

CAI band scale
CAI trend line
CAI lens gauges

What this system is

This system is a financial management platform built on a microservices architecture, separating a synchronous REST API from an asynchronous event-driven processing layer. The core-service exposes a REST API for managing clients, cards, and transactions, while the event-handler processes Kafka streams to persist financial entities. The infrastructure supports local development with PostgreSQL, Kafka, and Debezium for change data capture.

Features

Add Docker Compose configuration for microservices and event streaming infrastructure

The application now provides a complete local development environment via Docker Compose, defining services for the Java backend (port 8080) and an event handler (port 8081). The configuration also provisions a PostgreSQL database with logical replication enabled, a Zookeeper and Kafka cluster for event streaming, and a Debezium Connect instance for change data capture. Environment variables for database credentials, JWT secrets, and Kafka/Debezium settings are managed through a new .env.example file.

(repo-wide) · high confidence

Added Debezium PostgreSQL connector configuration

A new configuration file (conf/postgres-connector.json) and a helper script (conf/run.sh) have been added to set up a Debezium PostgreSQL connector. The configuration defines a Kafka Connect source connector that streams the 'public.events' table from a local PostgreSQL instance to Kafka, using the pgoutput plugin and applying transformations to unwrap and route the data.

conf · high confidence

Introduce common domain models, repositories, and query services

Added new domain models for Account, Card, Client, and Transaction, along with their corresponding Spring Data JPA repositories. The change also introduces a generic QueryService interface and specific implementations for each entity, enabling standardized read operations across the application's core business entities.

common · high confidence

Introduce core-service with REST API for client, card, and transaction management

The core-service now exposes a REST API for managing clients, cards, and transactions. Users can register and log in via the /api/v1/auth endpoints, which issue JWT access and refresh tokens. The /api/v1/clients endpoints allow retrieving client details, their associated cards, and account information. Card creation and retrieval are available at /api/v1/cards, including fetching transactions for a specific card. Transaction creation and retrieval are handled at /api/v1/transactions. The service implements a layered architecture with controllers, services, and mappers, and includes global exception handling for validation, authentication, and access denial errors.

core-service · high confidence

Introduce event-driven processing for financial entities

The event-handler module now implements a Kafka-based event processing system that listens for create events for Accounts, Cards, Clients, and Transactions. Each event is routed to a dedicated handler (e.g., AccountCreateEventHandler) which deserializes the payload using Gson and persists the entity via a corresponding service (e.g., AccountService). The system includes configuration for JSON deserialization of LocalDateTime and manual Kafka acknowledgment.

event-handler · high confidence

Dependencies

Initial project structure with Maven multi-module build

The project is initialized with a Maven multi-module structure, defining parent and child POMs for 'common', 'core-service', and 'event-handler' modules. This establishes the build configuration for the application, including dependencies for Spring Boot 3.2.5, PostgreSQL 42.7.3, Liquibase 4.27.0, Lombok 1.18.32, and Spring Kafka 3.1.4.

(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 48 → 50 (+1.8)
  • Rubric changed (rubric-2026.10.5 → rubric-2026.11.2) — scores are not directly comparable.

Lenses

  • Code Health 63 → 63 (+0.0)
  • Architecture 87 → 86 (-0.5)
  • Maturity 40 → 46 (+6.2)
  • Readiness 38 → 38 (+0.0)
  • Security 85 → 88 (+3.5)

Resolved (1)

  • Documentation: no contributor guidance (README.md)

New (1)

  • High interface indirection

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

Survey your own repository

SpringBootCourses/cqrs-banking-app 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 d66db15501d9f4e5f076016ab10bcd87d698053f — 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.